Re: start-stop-daemon : questions about retry
Hi Darac,
unfortunately that’s already the case. But today I have a different behaviour. Cherokee stops, but doesn't kill php-cgi. Very very wierd.
# ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 1294 0.1 0.7 193960 44688 ? S Jan09 1:07 php-cgi -b 127.0.0.1:47990
root 1374 0.0 0.0 24712 764 ? Ssl Jan09 0:00 /usr/local/sbin/cherokee -d
www-data 1376 0.0 0.1 794328 10528 ? Sl Jan09 0:01 /usr/local/sbin/cherokee-worker
www-data 1378 0.0 0.0 76372 2156 ? S Jan09 0:00 /usr/bin/rrdtool -
[…]
# cat /usr/local/var/run/cherokee.pid
1374
# start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile /usr/local/var/run/cherokee.pid --name cherokee
#ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 1294 0.1 0.7 193960 44688 ? S Jan09 1:08 php-cgi -b 127.0.0.1:47990
[…]
Does this have something to do with the script, or with cherokee?
Cheers
Stadtpirat
________________________________
Von: Darac Marjal <mailinglist@darac.org.uk>
An: debian-user@lists.debian.org
Gesendet: 12:32 Montag, 7.Januar 2013
Betreff: Re: start-stop-daemon : questions about retry
On Sun, Jan 06, 2013 at 02:10:43AM -0800, - - wrote:
> Hello,
>
> I am trying to write an init script for cherokee webserver. Not, there is already one, but I wanted to have one derived from skeleton.
>
>
>
> In function "do_stop()" the script executes this line:
> "start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME"
Right, I believe that this will find a process with the name $NAME and
the pid specified in $PIDFILE and then send SIGTERM to that process,
wait 30 seconds, then SIGKILL and wait 5 seconds (if the process stops
within that 35 seconds, that's good, otherwise s-s-d will return 2).
So, probably the first thing to check is that $PIDFILE and $NAME have
the values you want and that $PIDFILE exists and has a pid stored in it.
>
> But nothing happens. I get exit code 1, which means that the daemon was already stopped. But that is not true. The daemon was still running and not cherokee, nor it's subprocesses were stopped.
>
> Am I doing something wrong here?
>
> THanks
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 1357467043.90187.YahooMailNeo@web140506.mail.bf1.yahoo.com">http://lists.debian.org/[🔎] 1357467043.90187.YahooMailNeo@web140506.mail.bf1.yahoo.com
>
Reply to: