As a further discovery I found this in one of my startup log files. It
explains why dbus.socket didn't start:
Apr 15 09:51:18 allie kernel: [ 6.223804] systemd[1]: Found ordering
cycle on basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.223996] systemd[1]: Walked on cycle
path to sockets.target/start
Apr 15 09:51:18 allie kernel: [ 6.224185] systemd[1]: Walked on cycle
path to dbus.socket/start
Apr 15 09:51:18 allie kernel: [ 6.224370] systemd[1]: Walked on cycle
path to sysinit.target/start
Apr 15 09:51:18 allie kernel: [ 6.224559] systemd[1]: Walked on cycle
path to rpcbind.service/start
Apr 15 09:51:18 allie kernel: [ 6.224744] systemd[1]: Walked on cycle
path to basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.224931] systemd[1]: Breaking
ordering cycle by deleting job dbus.socket/start
Apr 15 09:51:18 allie kernel: [ 6.225152] systemd[1]: Found ordering
cycle on basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.225337] systemd[1]: Walked on cycle
path to sockets.target/start
Apr 15 09:51:18 allie kernel: [ 6.225526] systemd[1]: Walked on cycle
path to avahi-daemon.socket/start
Apr 15 09:51:18 allie kernel: [ 6.225716] systemd[1]: Walked on cycle
path to sysinit.target/start
Apr 15 09:51:18 allie kernel: [ 6.225905] systemd[1]: Walked on cycle
path to rpcbind.service/start
Apr 15 09:51:18 allie kernel: [ 6.226094] systemd[1]: Walked on cycle
path to basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.226283] systemd[1]: Breaking
ordering cycle by deleting job avahi-daemon.socket/start
Apr 15 09:51:18 allie kernel: [ 6.226506] systemd[1]: Found ordering
cycle on basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.226689] systemd[1]: Walked on cycle
path to sysinit.target/start
Apr 15 09:51:18 allie kernel: [ 6.226878] systemd[1]: Walked on cycle
path to rpcbind.service/start
Apr 15 09:51:18 allie kernel: [ 6.227066] systemd[1]: Walked on cycle
path to basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.227253] systemd[1]: Breaking
ordering cycle by deleting job rpcbind.service/start
Apr 15 09:51:18 allie kernel: [ 6.227475] systemd[1]: Found ordering
cycle on basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.227670] systemd[1]: Walked on cycle
path to sysinit.target/start
Apr 15 09:51:18 allie kernel: [ 6.227857] systemd[1]: Walked on cycle
path to nfs-common.service/start
Apr 15 09:51:18 allie kernel: [ 6.228043] systemd[1]: Walked on cycle
path to basic.target/start
Apr 15 09:51:18 allie kernel: [ 6.228230] systemd[1]: Breaking
ordering cycle by deleting job nfs-common.service/start
However, it raises a new question. Why is there a cycle... It looks like
nfs-common and rpcbind are both wanted by sysinit, but I can't see why...
Given that this is breaking the startup pretty badly to have these nfs
services in there, I'm going to look at removing them...
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
