Bug#806949: ifupdown: some tweaks to networking.service

[Michael Biebl]

Am 23.12.2015 um 23:03 schrieb Bob Proulx:
> Martin Pitt wrote:
>> Michael Biebl wrote:
>>> I still think though, that we should consider allow-hotplug interfaces
>>> when dealing with network-online.target.
>>>
>>> The reason is, that the debian installer uses allow-hotplug by default.
>>
>> Argh, this is indeed a tremendously bad default. So far I had the
>> impression that "auto" is for "must be present for booting", and
>> "allow-hotplug" is for "bring it up when present, but don't block on
>> it on boot". But if the installer always uses allow-hotplug, then I
>> think that completely defies trying to make any difference between the
>> two.
> 
> If a client system requires an NFS mounted file system then the admin
> must configure the network to be "auto" and not "allow-hotplug".
> The simple reason is that because otherwise it won't work. :-)

That's not quite acurate. The if-up.d hook scripts did work for
allow-hotplug under sysvinit. It just meant, the NFS share was mounted
at an arbitrary point during boot.
So allow-hotplug and SysV init scripts with Required-Start: $network was
not a good combination.

Under systemd mounting works a bit differently and fails hard if network
is not yet up when the remote mounts are triggered.

So this is a regression compared to wheezy.


-- 
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/20151224/49566bee/attachment-0002.sig>