Ron Olsen;178055 Wrote: > That's good to know! zap, eh? Must be a feature of start-stop-daemon, > since "zap" does not appear as an option in the /etc/init.d/slimserver > script. It must kill the process, if it exists, and delete the > /var/run/slimserver/slimserver.pid file. > > If SS dies unexpectedly, the /var/run/slimserver/slimserver.pid file > will still be around. Then when you do a /etc/init.d/slimserver start, > it sees the pid file and thinks slimserver is already running. > > That's why you have to manually delete this file after an unexpected SS > crash, or you'll get the "already running" error when you try to start > SS via "/etc/init.d/slimserver start".
This interpretation of how "zap" works is wrong. Gentoo init scripts maintain a separate "script status" that is independent of processes actually running, or any process pid file that may exist. This status can become incorrect when a process crashes. The init script status is still "started", but there are no processes running. When you try to start the script again, you'll get the message that it's already started. "Zap" changes the status back to "stopped". It does nothing about actually stopping processes or deleting pid files. You can run "rc-status" to see the status of all your scripts. See "Tips and Tricks" in http://www.gentoo.org/news/en/gwn/20041018-newsletter.xml for more details on Gentoo init script options. -- Ron Olsen ------------------------------------------------------------------------ Ron Olsen's Profile: http://forums.slimdevices.com/member.php?userid=9233 View this thread: http://forums.slimdevices.com/showthread.php?t=32451 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
