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 mean that systemd shouldn't be able to do a better job of
ignoring the problem. Perhaps, if it sees rcS and rcN runlevels for a
service, it should demote them to rcN and issue a big fat warning.
Thanks for looking anyway
Christian
On 16/04/11 01:24 AM, Tollef Fog Heen wrote:
]] 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 systemd are already dependent on basic.target. This causes
| a loop and the loop breaking kills (among other things!) dbus.socket
| to break the loop. This is NOT GOOD.
Well, the circular depends are the problem, not the loop breaking. The
problem is that nfs-common and rcpbind both try to start in rcS.d and
rcN.d. It's not at all clear why some maintainers thinks that makes any
sort of sense.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
