Something to try (in all your free time)? let the system run nicely without rmsgw, then turn it on for a bit and if you catch the netstat output with an empty or null value, stop/start ax25d.? Does it become stable again?
? Hi Jon,
I think you make a very good point here; ax25d is a wrapper to rmsgw, much like inetd was a wrapper to telnet way back in the day. ?If I recall, the wrapper handles binding to the interface and listening for connections. ?When a connection happens, it forks and execs the process (e.g. rmsgw, telnet), leaving the child with a set of open file handles to manipulate the connection. ?Put another way, both ax25d and rmsgw interact with the kernel's ax25 stack, so either could be responsible.
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. ?Assuming nothing happens after a day, I'll modify the test, letting rmsgw run until the kernel state is triggered and try restarting ax25d to see what happens to netstat.
? Cheers
? Mike
