On 7 April 2016 at 12:51, Wouter Verhelst <wou...@debian.org> wrote: > On Thu, Apr 07, 2016 at 01:04:28PM +0300, Alkis Georgopoulos wrote: >> One side effect of this issue is that it prohibits network-manager from >> starting, because systemd sometimes deletes it to break the dependency >> cycle: >> https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679 >> >> pitti there suggested a quick fix of setting "Default-Start:" to "2 3 4 5" >> instead of "S". >> Is that a reasonable thing to do until the implementation with the >> nbd-generators is released? > > Maybe. > > The reason nbd is in runlevel S is because it needs to run before > mountnfs.sh, otherwise filesystems won't be mounted properly. The init > script has a line "X-Start-Before: mountnfs" to enforce that. It could > work if either Ubuntu doesn't support non-systemd installs anymore, or > if mountnfs (or its systemd equivalent) has been moved out of S as well.
All services in runlevels 2-5 get implicitly a dependency After=basic.target basic.target has 'RequiresMountsFor=/var /var/tmp', so this can only work if neither of those directories are nfs-mounted. So, it could work on a (possibly large) number of setups, but not everywhere. -- Saludos, Felipe Sateler
