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

[Michael Biebl]

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 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

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?
Why should ifupdown tear down the network on shutdown then?


Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151230/d01c5593/attachment-0002.sig>