@rerwin - sorry, I caused the failure, by manually removing old sns first. This time I just installed sns 2.3.1 over the top and I'm posting from it.
Will continue to test sns stability over next week.
Please keep the "set -x" edit for rc.network; the one in sns is probably not needed. If you see the failure to reconnect, grab and post the file:
/tmp/bootsysinit.log
so that I can see why.
B.K. Johnson,
SNS 2.3+ has the version in the window title. So your version is older than that.
If you need to know which older version you have, look in:
/usr/local/simple_network_setup/sns.
I take your point about supporting '--version', which I intend to add.
Richard
I discovered that attempting to reconnect with the simple_network_setup network manager, the reconnect would fail because dhcpcd was already running! This was caused by networkdisconnect not stopping SNS correctly.
I saw this with my single-core PC but not with the dual-core PC. But the latter was responding to a false indication that the link was still "up".
The fix adds invocation of the SNS rc.network "stop" option, to ensure that SNS kills the link according to its own logic, instead of the generic logic. Now all of the managers run their own termination code.
A short (0.1 sec.) delay was inserted for the generic code to ensure that a link is down. My assumption is that a second core/thread runs the link-down operation slower than the first core/thread runs before making the check for the link being down.
I discovered that the Error window was not displaying when an SNS connection attempt failed. Several years ago the definition of the window became corrupted, apparently during an editing session. In addition, I found that the SNS version was not showing in the main window, as I had intended in version 2.3.