After stopping x2gocleansessions through its initscript: /etc/init.d/x2gocleansessions stop I noticed that it was still showing up in the process list. Starting it up again adds a new instance alongside the old, which will also refuse to stop via the script. Repeated restarts via the init script will keep creating more instances. They have to be killed manually. The id of the running process does match the one in its pid file when you attempt to stop the service. It seems to just be ignoring the stop signal from the start-stop-daemon command in its init script. Reproducible: Always Steps to Reproduce: 1. Start x2gocleansessions 2. Attempt to stop x2gocleansessions Actual Results: Background process continues running. Expected Results: Background process should terminate.
Tbanks for spotting this! A small leftover of x2goserver, the PID file created by x2gocleansessions is called x2goserver.pid (while the init script expects x2gocleansessions.pid) I fixed the init script in CVS, without a revision bump for now (I have a few things left to check/fix in x2goserver before making a revision bump to get all the fixes)
