Bug#809166: networking.service does not prevent ifdown with network file systems

On 21/01/2016 11:10 μμ, Guus Sliepen wrote: On Fri, Jan 15, 2016 at 09:14:52AM +0100, Guus Sliepen wrote: ifupdown 0.8.9 can also mark interfaces with the "no-auto-down" keyword, which causes those interfaces to be ignored during "ifdown -a". This is a more explicit way to tell an interface shou

Bug#809166: networking.service does not prevent ifdown with network file systems

Hey Guus, Guus Sliepen [2016-01-21 22:10 +0100]: > ifupdown version 0.8.9 will not bring the link down of manual interfaces > during shutdown (but every "down" and "post-down" keyword is still > executed). > > ifupdown 0.8.9 can also mark interfaces with the "no-auto-down" keyword, > which causes

Bug#809166: networking.service does not prevent ifdown with network file systems

On Fri, Jan 15, 2016 at 09:14:52AM +0100, Guus Sliepen wrote: > > The "manual" stanza isn't there just for network-manager. LTSP chroots don't > > have network-manager installed by default. > > A netbooted system needs these 2 things from ifupdown: > > 1) the scripts at /etc/network/if-up.d to get

Bug#809166: networking.service does not prevent ifdown with network file systems

About the boot process of LTSP clients, I think it's better not to focus on LTSP, but on the simplest possible netbooted system that works out of the box in all Debian/Ubuntu versions (and many other Linux distros) without using a custom initramfs: Let's say we have an "rw" NFS export for a sin

Bug#809166: networking.service does not prevent ifdown with network file systems

On Fri, Jan 15, 2016 at 09:37:31AM +0200, Alkis Georgopoulos wrote: > The "manual" stanza isn't there just for network-manager. LTSP chroots don't > have network-manager installed by default. > A netbooted system needs these 2 things from ifupdown: > 1) the scripts at /etc/network/if-up.d to get e

Bug#809166: networking.service does not prevent ifdown with network file systems

Hi, I'm the LTSP developer that added the "manual" stanza a few years ago (r1944). I've answered in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810934#10 about it, but I should probably add a comment here as well as this bug sees the issue from a different view. The "manual" stanza is

Bug#809166: networking.service does not prevent ifdown with network file systems

Martin Pitt [2016-01-13 23:30 +0100]: > I filed https://bugs.debian.org/XX, thanks Michael for pointing > out conf.d/. "Let's type this mail while I wait for the bug number" syndrome, sorry. It's . Martin -- Martin Pitt| http://www.piwar

Bug#809166: networking.service does not prevent ifdown with network file systems

Hey Guus, Guus Sliepen [2016-01-13 16:57 +0100]: > Great. Who shall do the honors of writing a patch/bug report? I filed https://bugs.debian.org/XX, thanks Michael for pointing out conf.d/. > > But independently of that: Do you actually think it is right that > > "ifdown" on a manual interfa

Bug#809166: networking.service does not prevent ifdown with network file systems

Am 13.01.2016 um 16:57 schrieb Guus Sliepen: > On Wed, Jan 13, 2016 at 04:43:33PM +0100, Martin Pitt wrote: > >>> [keyfile] >>> unmanaged-devices=interface-name=eth0 >> >> I guess it could do that. This is currently done in >> >> >> https://sources.debian.net/src/ltsp/5.5.5-1/client/share/ltsp/

Bug#809166: networking.service does not prevent ifdown with network file systems

On Wed, Jan 13, 2016 at 04:43:33PM +0100, Martin Pitt wrote: > > [keyfile] > > unmanaged-devices=interface-name=eth0 > > I guess it could do that. This is currently done in > > > https://sources.debian.net/src/ltsp/5.5.5-1/client/share/ltsp/init-ltsp.d/50-interfaces/ > > and it could be equa

Bug#809166: networking.service does not prevent ifdown with network file systems

Hey Guus, Guus Sliepen [2016-01-13 16:30 +0100]: > Ugh. That's totally wrong. Why doesn't LTSP tell NetworkManager itself > to stop messing with eth0? Instead of adding a stanza to /e/n/i, just > write this to /etc/NetworkManager/NetworkManager.conf: > > [keyfile] > unmanaged-devices=interface-na

Bug#809166: networking.service does not prevent ifdown with network file systems

On Wed, Jan 13, 2016 at 04:00:16PM +0100, Martin Pitt wrote: > > Why should ifupdown tear down the network on shutdown then? > > E. g. LTSP creates an ifupdown stanza like "iface eth0 inet manual" > for the remote root interface to prevent NetworkManager from > (auto-)connecting/disconnecting eth

Bug#809166: networking.service does not prevent ifdown with network file systems

Martin Pitt [2016-01-13 16:00 +0100]: > + * inet{,6}.defn: Don't down an interface when stopping. This got introduced > +in 0.8.5, but breaks use cases like LTSP which create a "manual" > +interfaces stanza to prevent NetworkManager or other management software > +to *prevent* touching

Bug#809166: networking.service does not prevent ifdown with network file systems

Hello Guus, Michael, sorry, took a bit to get back to this. I did some research about this now. Michael Biebl [2015-12-30 19:41 +0100]: > Can you actually use ifupdown for that? > If your / is on a network file system you most likely need to setup your > network via the initramfs, or not? Correc

Bug#809166: networking.service does not prevent ifdown with network file systems

Am 30.12.2015 um 13:26 schrieb Martin Pitt: > Hello Guus, > > Guus Sliepen [2015-12-28 11:08 +0100]: >> Hm, but shouldn't systemd (with networking.service from ifupdown 0.8.4) >> order the unmounting of the NFS/iSCSI partitions before stoppping the >> network interfaces? > > This works for /home

Bug#809166: networking.service does not prevent ifdown with network file systems

Hello Guus, Guus Sliepen [2015-12-28 11:08 +0100]: > Hm, but shouldn't systemd (with networking.service from ifupdown 0.8.4) > order the unmounting of the NFS/iSCSI partitions before stoppping the > network interfaces? This works for /home and other "sub"mounts, and there systemd should indeed fi

Bug#809166: networking.service does not prevent ifdown with network file systems

On Mon, Dec 28, 2015 at 08:13:18AM +0100, Martin Pitt wrote: > > Please check if the problem still exists with version 0.8.4. Version 0.8 > > didn't correctly order itself with respect to network-online.target, but > > 0.8.4 should have fixed that. > > This should be unrelated to network-online.t

Bug#809166: networking.service does not prevent ifdown with network file systems

Hey Guus, Guus Sliepen [2015-12-27 20:50 +0100]: > Please check if the problem still exists with version 0.8.4. Version 0.8 > didn't correctly order itself with respect to network-online.target, but > 0.8.4 should have fixed that. This should be unrelated to network-online.target. networking.serv

Bug#809166: networking.service does not prevent ifdown with network file systems

On Sun, Dec 27, 2015 at 07:58:06PM +0100, Martin Pitt wrote: > Package: ifupdown > Version: 0.8 > > /etc/init.d/networking has some functionality to check if the root > file system or swap are on a network file system, in > check_network_file_systems() and check_network_swap(). In that case, > th

Bug#809166: networking.service does not prevent ifdown with network file systems

Package: ifupdown Version: 0.8 Hello, /etc/init.d/networking has some functionality to check if the root file system or swap are on a network file system, in check_network_file_systems() and check_network_swap(). In that case, the interfaces are not ifdown'ed during shutdown, so that these networ