Re: exim init.d script problem

[Adam Heath <doogie@debian.org>]

On Fri, 26 Mar 2004, Ferenc Engard wrote:

> Dear Mark and dpkg Team,
>
> The following command on my debian unstable box:
>
> root:~/tmp# start-stop-daemon --start --pidfile /var/run/exim/exim.pid
> --exec /usr/lib/exim/exim3 -- -bd
>
> Results in the following pid file:
>
> root:~/tmp# ls -l /var/run/exim/
> total 4
> -rw-r--r--    1 root     mail            6 Mar 26 23:29 exim.pid-bd
>
> And the following works good:
>
> root:~/tmp# start-stop-daemon --start --pidfile /var/run/exim/exim.pid
> --exec /usr/lib/exim/exim3 -- -bd -q30m
> root:~/tmp# ls -l /var/run/exim/
> total 4
> -rw-r--r--    1 root     mail            6 Mar 26 23:30 exim.pid
>
> (FYI, I use exim3 with exiscan, that's why I have to remove the -q30m
> switch.)
>
> I suppose this is a start-stop-daemon problem, but for safety's sake, I
> have sent it to the exim3 maintainer Mark Baker, too.

exim is forking into the background, because you are using -bd.  And when you
give --pidfile to s-s-d, it attempts to find the process named in the file,
which doesn't exist anymore.

This is not a dpkg bug.