Bug#921827: exim4: Restarting exim4 on a sysvinit system doesn't work properly

[Andreas Metzler]

On 2019-02-09 Elimar Riesebieter <riesebie at lxtec.de> wrote:
> Package: exim4
> Version: 4.92~RC5-2
> Severity: important


> Dear maintainer,

> restarting exim4 on a sysvinit system does not close an existing exim4
> daemon. paniclog gives: 2019-02-09 00:07:21 socket bind() to port 25
> for address (any IPv4) failed: Address already in use: daemon
> abandoned

> I think this is due to a new start-stop-daemon rule which is like:
> "matching only on non-root pidfile ... is insecure"

> I don't have an exim4 running on a systemd machine so can't test
> there.

> FMPOV this should be severity serious.

Are you sure that you get this behavior /with/ 4.92~RC5-2 and not when
upgrading from 4.92~RC5-1 *to* 4.92~RC5-2, i.e. the failing
"invoke-rc.d exim4 stop" was using the
broken-with-newer-start-stop-daemon old init script?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'