Hi. On Tue, 31 Jul 2018 10:42:42 -0700 Rick Stevens wrote:
> On 07/31/2018 10:23 AM, francis.montag...@inria.fr wrote: >>> If you don't have the automount stuff, I think the most reliable thing >>> is to give your client a fixed IP/netmask/gateway combination. ... >> This may not be sufficient: I had a client with fixed IP configuration >> that fails to mount an NFS server at boot. > Yes, I realize this. This is one of the issues with systemd in general, > it parallelizes stuff and causes these race conditions. Not quite the problem IMO. systemd parallelizes yes, but offers (various) ways to specify dependencies for proper ordering. This problem is here with NetworkManager that starts asynchronously. Note also that NetworkManager was adopted far before systemd. And thanks to systemd to allow overloading/overriding the configurations of the system *without* modifying a configuration file but by adding a drop-in .conf file. In this case, it allows you to specify what you want for "the network is up". One may for example extend this from: the default: nm-online -s -q --timeout=30 to (the choice I made): routes defined and gateway reachable or to: routes defined and gateway reachable and DNS servers reachable -- francis _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/PMTILCGS7ZKRJHO7TJYVRL4QNEIJJPIU/
