HOW TO Start Up JNOS

Four files are required for JNOS autostart at power up: 

sample.rc.local
startup-jnos
start-main
start-loop

These files are included in the standard templfiles tar archive.

Sample.rc.local
---------------
Location:  JNOS docs sub-directory.
This files shows how to edit your /etc/rc.local file to call startup-jnos.  
/etc/rc.local is run when Linux boots into any of the multiuser modes.  

Be careful when editing the sample.rc.local file since it may contain
commands for other applications.  Make sure that "exit 0" remains the last line in the file.

 
startup-jnos
start-main
start-loop
------------
Location:  main JNOS directory
These three files are used to startup JNOS in a continuos loop.

Startup-jnos is called from /etc/rc.local.  It simply calls the start-main
script and redirects output to log files.  This makes it simple to use
startup-jnos at the command line without having to define output redirection.

start-main calls start-loop within the Linux screen command.  The screen
command allows attaching and detaching from the JNOS console from remote
terminal sessions.  start-main also calls an iptables script to secure
the tunnel between Linux and JNOS.  The iptables commands can be bypassed
with the -j options.

start-loop calls jnos.exe in a continuous loop that is only exited if JNOS
terminates with an exit code of 0 (zero).  This will restart JNOS in case
it suffers some fault and terminates with a non-zero exit code.
This allows a remote sysop to connect to JNOS over a radio link, issue the
mbox password to gain access to the JNOS console command line, and restart
JNOS by issuing a non-zero exit code.  "exit 99" is recommended for
consistency.

Examples
--------
To start JNOS in a loop, for the first time:
	sudo ./startup-jnos

To start JNOS in a loop, if it was previously started:
	sudo ./startup-jnos -j

To exit JNOS and cause a restart:
	exit 99

To exit JNOS and cause the start-loop script to exit:
	exit 0

Check for proper TNC Communications After Startup
-------------------------------------------------
It is a good idea to check for proper TNC communications after startup.
A system configured according to county standards will have the first
beacons appear in the F9 log.

So, press F9 to see the log.  A properly formatted beacon will look
similar to:

    Wed Nov  3 19:39:05 2010 - p144 sent:
    KISS: Port 0 Data
    AX25: N6MEF-1->ID UI pid=Text
    0000  Santa Clara County ARES/RACES - Cupertino - CF Ver 95

Any extraneous TNC commands in the log indicate that there was a problem
communicating with the TNC.  Try stopping and restarting JNOS.