When net.wlan0 starts up, it goes to 'Backgrounding' and services that need net are postponed until that net.wlan0 has finished starting. ntp-client is listed to start 'after net' but not 'need net'. This results in ntp-client failing to set the clock because it happens before net.wlan0 has finished starting. If I change 'after net' to 'need net', then it waits for net.wlan0 and starts succesfully. Reproducible: Always Steps to Reproduce: 1. Reboot computer Actual Results: Exiting, name server cannot be used: Temporary failure in name resolution (-3) * Failed to set clock * ERROR: ntp-client failed to start Expected Results: ntp-client should wait until net.wlan0 has started before it starts.
# emerge -pv baselayout openrc ntp .... [ebuild R ] sys-apps/baselayout-2.1-r1 USE="-build" 40 kB [ebuild R ] sys-apps/openrc-0.11.8 USE="ncurses pam unicode -debug -newnet (-prefix) (-selinux) -static-libs" 171 kB [ebuild R ] net-misc/ntp-4.2.6_p5-r1 USE="ipv6 ssl vim-syntax -caps -debug -openntpd -parse-clocks -samba (-selinux) -snmp -zeroconf" 0 kB
*** This bug has been marked as a duplicate of bug 439564 ***