Le mardi 04 avril 2006 à 12:48 +0200, Peter Palfrader a écrit : > Package: and > Version: 1.2.1-2 > Severity: serious > > Hi, > > | simona:~# ps xauf | grep and | grep -v grep > | simona:~# [ -f /var/run/and.pid ] || echo 'does not exist' > | does not exist > | simona:~# /etc/init.d/and start > | Starting auto nice daemon: and. > | simona:~# ps xauf | grep and | grep -v grep > | root 20614 0.0 0.0 2800 732 ? S 12:46 0:00 /usr/sbin/and > | simona:~# cat /var/run/and.pid > | 20613 > | simona:~# start-stop-daemon --stop --pidfile /var/run/and.pid --exec > /usr/sbin/and > | No /usr/sbin/and found running; none killed. > > Since and forks after you start it, and you create the pidfile from > start-stop-daemon the pidfile is wrong. so stop never kills and. > > Please either fix and to > - to write the pidfile on its own, or > - not fork (and let start stop daemon detach), or > - do not check the pidfile when killing and. > (in order of preference).
I've been thinking about this for a while now... I don't like your solution, as it involves even more tools to make it work. Wouldn't it be enough if I suppress "--make-pidfile" and "--pidfile" from the start and stop? This way, it would base it start and stop on the name of the process, and I don't think that any other process is going to be called "and". What do you think? Of course, it would be preferable to have and upstream write his own pidfile. Hope it helps. > Thanks, > Peter -- Jérôme Warnier FLOSS Consultant http://beeznest.net
