Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On Thu, Apr 28, 2016 at 10:13:52AM -0300, Felipe Sateler wrote: > On 28 April 2016 at 09:26, Alkis Georgopoulos wrote: > Wouter wrote: > > The reason nbd is in runlevel S is because it needs to run before > > mountnfs.sh, otherwise filesystems won't be mounted properly. > >

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On 28 April 2016 at 09:26, Alkis Georgopoulos wrote: > On 28/04/2016 03:05 μμ, Felipe Sateler wrote: >> >> If you don't need the service you can mask it (create a symlink from >> /etc/systemd/system/nbd-client.service to /dec/null). > > > I'm involved in this bug report as

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On 28/04/2016 03:05 μμ, Felipe Sateler wrote: If you don't need the service you can mask it (create a symlink from /etc/systemd/system/nbd-client.service to /dec/null). I'm involved in this bug report as upstream developer for LTSP and as Debian co-maintainer for it, i.e. I'm trying to care

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On 28 Apr 2016 08:46, "Alkis Georgopoulos" wrote: > > On 26/04/2016 11:16 μμ, Wouter Verhelst wrote: >> >> One workaround is to not combine NetworkManager and nbd-client on the >> same system. If you're going to try to run an important filesystem (say, >> the root filesystem) on

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On 26/04/2016 11:16 μμ, Wouter Verhelst wrote: One workaround is to not combine NetworkManager and nbd-client on the same system. If you're going to try to run an important filesystem (say, the root filesystem) on something that lives somewhere on the network, giving the user the ability to play

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

Hi Alkis, On Mon, Apr 25, 2016 at 01:15:26PM +0300, Alkis Georgopoulos wrote: > Unfortunately, testing showed that replacing: > # Default-Start: S > with: > # Default-Start: 2 3 4 5 > doesn't solve the issue. > > One workaround is to change instead: > # Required-Start: $network $local_fs > with:

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

Unfortunately, testing showed that replacing: # Default-Start: S with: # Default-Start: 2 3 4 5 doesn't solve the issue. One workaround is to change instead: # Required-Start: $network $local_fs with: # Required-Start: $local_fs This solves the ordering cycle by starting nbd-client a little

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On 7 April 2016 at 12:51, Wouter Verhelst 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:

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

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

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

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

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

On Sat, Aug 22, 2015 at 10:42:00PM -0300, fsate...@debian.org wrote: Please add a systemd unit for the given service with the appropriate dependencies, which most of the time will be less strict than Before=sysinit.target. In other cases, the script is simply not applicable in systemd, in