If the system reboots without proper shutdown (i.e. due to a power failure, or a watchdog hang) the command "nxserver --start" fails (NX> 500 ERROR: Service already running), so nxserver init script does not start, so nxserver init script is not executed at system shutdown, so "nxserver --stop" is not executed at system shutdown. The init script will never start again until someone gives the "nxserver --stop" command manually. init script should return 0 also if "nxserver --start" command fails. Reproducible: Always
Created attachment 148572 [details, diff] fix for the nxserver init script
OK in CVS, I've added session cleaning in the stop part (sample init script from upstream also does it). As for the return code in start, nxserver-freeedition returns 0 when the service is already started (which is correct, as the service is started indeed). I'll check with freenx upstream if this can be fixed directly in the server
*** Bug 216837 has been marked as a duplicate of this bug. ***
OK, patch is being reviewed upstream, adding to net-misc/nxserver-freenx-0.7.2-r2 in portage in the meantime Thanks for the reports and suggestions all