I'll try the test the way you describe it (run ax25d, comment out rmsgw), but I don't think I'll get the correct kernel state with out rmsgw. ?Setup this way, there is no "LISTEN" entry, so the kernel likely doesn't have the correct kernel structures loaded.
? So, I tried testing this way, but I messed up the test; I haven't fixed persistent device names for my usb audio, so the AX.25 stack was down for a couple of days before I noticed.
? Instead of starting over, I took a peek at my PROD Pi, which has been healthy for over 3 weeks since turning off my mail check schedule. ?With 27 days of uptime, PROD finally encountered the "(null)" column in netstat output. ?PROD had been running rmsgw from ax25d during those 27 days and I've had about 6 connections to the gateway in that time. ?I decided to stop and restart ax25d. ?The stop cleared out the netstat entries, as you would expect when the service isn't listening any more. ?However, when I tried to start ax25d again, the system immediately crashed. ?I think that proves the bad state is held in the kernel and is not resolved by releasing the listening socket.
? Cheers
? Mike
