Bug#825870: sysvinit-utils: Second stop command does not use process matchers name and pidfile

Ah, now I see the rm -f $PIDFILE haha. So yeah you're right. On May 31, 2016 17:40, "Andreas Henriksson" wrote: > Hello Steven Roose. > > On Tue, May 31, 2016 at 02:15:10AM +0200, Steven Roose wrote: > [...] > > The daemon does not make it's own pidfile, so I added following

Bug#825870: sysvinit-utils: Second stop command does not use process matchers name and pidfile

Hello Steven Roose. On Tue, May 31, 2016 at 02:15:10AM +0200, Steven Roose wrote: [...] > The daemon does not make it's own pidfile, so I added following relevant > variables: > PIDFILE=/pidfile > START_ARGS=" --make-pidfile" > STOP_ARGS=" --remove-pidfile" [...] > --- a/debian/init-d-script >

Bug#825870: sysvinit-utils: Second stop command does not use process matchers name and pidfile

Are you sure? If that is the case, that what is --remove-pidfile for? I thought to understand from the docs that --pidfile is only used to identify the process, but thst start-stop-daemon considers pidfile handling to he done by the daemon. And that --make-pidfile and --remove-pidfile are to

Bug#825870: sysvinit-utils: Second stop command does not use process matchers name and pidfile

Package: sysvinit-utils Version: 2.88dsf-59 Severity: normal Tags: patch Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I used /etc/init.d/skeleton to make a script for a daemon. The daemon does not make it's