Bug#889144: stricter PIDfile handling breaks several daemons

Michael Biebl biebl at debian.org
Sat Feb 3 02:02:34 GMT 2018


Am 02.02.2018 um 20:07 schrieb Sven Hartge:

> ulogd2 drops its priviliges on its own. It needs to start as root to
> connect to the netlink sockets.

So, ulogd2 creates a directory /run/ulog which is owned by ulog:ulog but
then creates the pid file /run/ulog/ulog.pid owned by root:root.

I assume if you overwrite /usr/lib/tmpfiles.d/ulogd2.conf by creating a
/etc/tmpfiles.d/ulogd2.conf containing

d /run/ulog 0755 root root - -

ulogd2 will start properly

I assume, ulogd2 should either ensure the pidfile is owned ulog:ulog or
change the run directory to match the permissions of the pid file.

Does munin-node have the same mismatch?
-- 
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/20180203/2208930c/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list