Bug#622881: Info received (Bug#622881: Acknowledgement (systemd with dbus requires /var/run/dbus/ directory at boot which isn't created))

2011-04-18 Thread Christian Weeks
I agree, the circularity is the problem, but the means of resolving the circular depends is clearly a bit lacking if it results in killing essential services for trivial ones that are just badly configured. I agree that the nfs-common and rpcbind services are both in the wrong, but it doesn't

Bug#622881: Info received (Bug#622881: Acknowledgement (systemd with dbus requires /var/run/dbus/ directory at boot which isn't created))

2011-04-15 Thread Tollef Fog Heen
]] Christian Weeks | OK, so I've found the root cause. nfs-common and rpcbind both have | Default-Start: S and create symlinks in /etc/rcS.d/ This appears to | confuse systemd which makes them a dependent of | sysinit.target. nfs-common.service and rpcbind.service meta-services | created by syste

Bug#622881: Info received (Bug#622881: Acknowledgement (systemd with dbus requires /var/run/dbus/ directory at boot which isn't created))

2011-04-15 Thread Christian Weeks
retitle systemd causes dbus socket init failure if sysv init files are flagged as Default-start:S thanks OK, so I've found the root cause. nfs-common and rpcbind both have Default-Start: S and create symlinks in /etc/rcS.d/ This appears to confuse systemd which makes them a dependent of sysini