Am 27.11.2014 um 15:59 schrieb Michael Biebl: > I would have expected, that the socket does *not* exist before systemd > is re-execd, but apparently I had a file there: > > srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify > > and no process listening on it. > (don't worry about the date, it was run in a VM with a busted clock). > > *Some* process is triggering the creation of the notification socket and > it also seems to have the wrong permissions (should be srwxrwxrwx).
It's actually a bit simpler: v44 *did* already use /run/systemd/notify (with permissions srw-rw-rw-), then it was changed to use an abstract namespace and it was changed back and forth a couple of times. Maybe a simple chmod will do when upgrading from v44. Will test. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
