Bug#771101: Bug#761306: Bug#771101: wheezy -> jessie dist-upgrade failure when systemd is the active PID1

[Michael Biebl]

Am 27.11.2014 um 16:41 schrieb Michael Biebl:
> 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.

Just tested, a "chmod 777" is not sufficient. systemd will still fail to
bind to the socket. Only removing it and letting systemd create it on
daemon-reexec seems to do the trick.


-- 
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: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141127/076b703a/attachment-0002.sig>