Le 28/10/18 à 13:09, Laurent Bigonville a écrit :
Le 28/10/18 à 12:10, Guus Sliepen a écrit :
On Sun, Oct 28, 2018 at 11:41:17AM +0100, Laurent Bigonville wrote:

Any reasons why ifupdown-wait-online.service is not enabled by default?

Having a functional network-online.target by default seems to be
essential to me (ie. working NFS/network shares).

Am I overlooking something?
Only the fact that not everyone needs working NFS/network shares.
Consider people with laptops that might not have an Internet connection
when they boot their machine. Having to wait one and a half minute for
ifupdown-wait-online to time out would be very annoying to them.

Another issue is that a working network connection still doesn't imply
that you will get a working NFS mount. If you really depend on NFS, then
the service that does the NFS mount should wait for the NFS server to
become reachable and the mount to succeed.

NFS/network share was just an example, any service can have a dependency against the network-online.target.

And don't forget that network-online.target is not pulled in the dependency chain by default, at least one service on the system needs to declare a Wants=network-online.target. And if a service really declare a Wants=network-online.target, all the components on the system should honor that IMHO.

https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

TBH I opened this bug because I'm seeing a lot of people complaining on reddit[0] because of broken network share or service being started at wrong time due bogus ordering during boot.

On stretch, changing allow-hotplug to auto seems to be enough to fix the issue. So basically the problem is that allow-hotplug is not waiting for the DHCP to be up for example. Why are network interfaces created by the installed with allow-hotplug and not auto by default in the first place?

Question, isn't calling wait-online.sh script with WAIT_ONLINE_METHOD set to "ifup" the same as setting the interface as auto?

[0] https://www.reddit.com/r/debian/comments/9rvj0j/cifs_shares_not_mounting_at_boot/

Reply via email to