I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following:
Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start
Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start
Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start
Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated.
$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
$ apt-cache policy nbd-client ch.archive. ubuntu. com/ubuntu/ vivid-updates/main amd64 Packages security. ubuntu. com/ubuntu/ vivid-security/main amd64 Packages dpkg/status ch.archive. ubuntu. com/ubuntu/ vivid/main amd64 Packages
nbd-client:
Installed: 1:3.8-4ubuntu0.1
Candidate: 1:3.8-4ubuntu0.1
Version table:
*** 1:3.8-4ubuntu0.1 0
500 http://
500 http://
100 /var/lib/
1:3.8-4 0
500 http://
I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following:
Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client. service/ start service/ start service/ start deleted to break ordering cycle starting with basic.target/start
Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.
Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.
Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated.