[FADCA] AX25-DOWN Neglected

[C Schuman]

Last week I was asked to check on the Melbourne host and clean up the 
ax25-down script. I discovered that ax25-down was a mess and did an 
audit on some of the other hosts. What I discovered was... Ax25-down has 
been neglected. Every host is unique, not only in hardware, but in 
software selection and adoption. I have attempted to compose a "one size 
fits all" script.

FPAC does NOT detach the ROSE devices. Therefore you can not unload the 
ROSE and AX25 driver/modules. It really isn't necessary. It is necessary 
to detach the NetRom (nrX) and KISS (axX) devices.  The generic 
ax25-down does detach the KISS devices, but Not the NetRom  devices.

There are approx a half a doz programs that have to be stopped before 
you can shutdown the ax25 support. Judging from some of the script that 
I have looked at... this may have been a factor in the instability of 
some of our earlier systems. As long as the AX25 programs were run from 
the boot-up there was no problem, but after several ax25 restarts... the 
program inventory was a mess. We saw an example of this recently when 
the  Orlando host had four sessions of Mheardd running at once. The 
Mheard list was a full of duplicates!

The bottom line is this...
If you have to administer the host remotely you want to be able to stop 
ax25 cleanly before you restart. If however you have the host at your 
fingertips and restart by rebooting, you don't really need a clean 
software stop.

If you would like a copy of the ax25-down script or have a question... 
drop me a e-mail.

<<Charlie>>
     k4gbb