]] Matthias Berndt Hi,
| thank you for your reply. I do not have nfs-common installed, but the | problem may yet be the same. Here's an excerpt from my /var/log/dmesg: | | [ 5.413304] systemd[1]: Found ordering cycle on basic.target/start | [ 5.413312] systemd[1]: Walked on cycle path to sockets.target/start | [ 5.413319] systemd[1]: Walked on cycle path to dbus.socket/start | [ 5.413324] systemd[1]: Walked on cycle path to sysinit.target/start | [ 5.413330] systemd[1]: Walked on cycle path to setserial.service/start | [ 5.413335] systemd[1]: Walked on cycle path to basic.target/start | [ 5.413341] systemd[1]: Breaking ordering cycle by deleting job | dbus.socket/start | [ 5.413354] systemd[1]: Found ordering cycle on basic.target/start | [ 5.413360] systemd[1]: Walked on cycle path to sysinit.target/start | [ 5.413365] systemd[1]: Walked on cycle path to setserial.service/start | [ 5.413371] systemd[1]: Walked on cycle path to basic.target/start | [ 5.413376] systemd[1]: Breaking ordering cycle by deleting job | setserial.service/start I suspect # chkconfig: 2345 50 75 in the setserial init script might be to blame. Any chance you could remove that line and see if that fixes it? | It doesn't make any sense though. The only thing required for | setserial.service (which is not a proper systemd service unit but a | SysV init script service unit) is $remote_fs (or remote-fs.target), | which isn't involved in any of the two cycles above. Yeah, that should be ok, I think. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
