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

[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 and other "sub"mounts, and there systemd should
indeed figure out a correct ordering. (And it would be a systemd bug,
not an ifupdown bug if that isn't the case).

But not for the root partition -- that happens as the very last thing
(hardcoded in systemd-shutdown(8) after after all units got stopped.
That's what I meant with "unit ordering is irrelevant for this
problem".

I. e. if the root partition is on a network file system, we must never
tear down the network interfaces. But systemd does not know that
"networking.service" does that (it's just another unit which declares
that it wants to be stopped on shutdown and has an ExecStop=). In that
regard it is no different from sysvinit or upstart, which is why
/etc/init.d/networking carries this check.

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151230/7928efb8/attachment-0002.sig>