Bug#889144: stricter PIDfile handling breaks several daemons

[Sven Hartge]

Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl:

> 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.

Yes.

> 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.

It does. But there must be a reason for the directory to be owned by
ulog:ulog, no? What consequences does it have changing it? It may work for
my simple setup but then break again for other people.

> 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?

It has:

,----
| ds9:/run/munin# ls -al
| total 8
| drwxr-xr-x  2 munin root    80 Feb  3 13:15 .
| drwxr-xr-x 55 root  root  1880 Feb  3 02:57 ..
| -rw-r--r--  1 munin munin    7 Feb  3 13:15 munin-feds.ath.cx-skuld.feds.ath.cx.lock
| -rw-r--r--  1 munin munin    7 Feb  3 13:15 munin-svenhartge.de-www.svenhartge.de.lock
`----

But, as you can see, the directory is also used by the munin-updater
which is run as user "munin" so you can't make the directory owned by
root.

S°