Bug#889144: stricter PIDfile handling breaks several daemons

Michael Biebl email at michaelbiebl.de
Sun Feb 4 22:00:18 GMT 2018


Am 04.02.2018 um 21:26 schrieb Sven Hartge:
> On Sun, 4 Feb 2018 15:41:37 +0000 Simon Kelley <simon at thekelleys.org.uk>
> wrote:
> 
>> With my dnsmasq maintainer hat on, the current arrangement looks like this.
>>
>> 1) /run/dnsmasq is a directory owned by dnsmasq:nogroup
>> 2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops
>> root, so is root:root
>> 3) The reason /run/dnsmasq is owned by dnsmasq is so that dnsmasq can
>> unlink the pidfile at shutdown, after it has dropped root and is running
>> as 'dnsmasq'
> 
> Does dnsmasq need a PIDfile when running under systemd? Can't it just
> not double fork, stay in the foreground using a Type=simple systemd unit?
> 
> That way the whole problem could be avoided all together.

If other services depend on dnsmasq, please keep
https://www.lucas-nussbaum.net/blog/?p=877 in mind




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180204/42054052/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list