net: +nm shouldn't provoke races

Brief version: otherwise DNS resolving might fail to perform
until dnsmasq service restart or system reboot (ouch!).

The problem:

1) NetworkManager requires dnsmasq;
2) dnsmasq can win a race against dhcpcd on ethernet.

The result:

1) /etc/resolv.conf looks fine;
2) dnsmasq is running;
3) resolving beyond /etc/hosts fails.

Suggested-by: Mikhail Efremov <sem@altlinux.org>
This commit is contained in:
Michael Shigorin 2019-01-17 20:50:52 +03:00
parent a3f47946d4
commit 0184a3b7fc

View File

@ -1,4 +1,4 @@
+nm: use/net/nm/nodelay; @:
+nm: use/net/nm; @:
use/net: use/services
@$(call add_feature)
@ -21,6 +21,8 @@ use/net/nm: use/net
@$(call add,DEFAULT_SERVICES_ENABLE,NetworkManager ModemManager)
@$(call add,DEFAULT_SERVICES_ENABLE,livecd-save-nfs) # keep interface up
# NOT recommended unless you know what you're doing
# (e.g. dnsmasq can win a race against dhcpcd)
use/net/nm/nodelay: use/net/nm
@$(call add,DEFAULT_SERVICES_DISABLE,NetworkManager-wait-online)