Bug 466446

Summary:	net-misc/ntp-4.2.6_p5-r1: ntp-client does not wait for dns service
Product:	Gentoo Linux	Reporter:	Massimo Burcheri <burcheri.massimo+bugs-gentoo>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Massimo Burcheri 2013-04-19 08:38:55 UTC

/etc/init.d/ntp-client does not wait for dns service such as /etc/init.d/dnsmasq at startup.
So ntpdate fails if /etc/resolv.conf relies completely on localhost and dnsmasq.

/etc/init.d/ntp-client has "use dns" but would rather "need dns" or "after dns" as dependency.

Reproducible: Always

Comment 1 SpanKY gentoo-dev

2013-04-21 04:32:21 UTC

if you have dnsmasq in your runlevels, then 'use dns' works just fine

'need dns' makes no sense because many people don't have an init.d script that provides dns services, and because 'use' works just as fine

'after dns' also makes no sense when compared to 'use dns'

post your `emerge --info` as every bug report should have, and post an example boot log (look for rc.log in /var/log/), and post `rc-status --all`.

Comment 2 Massimo Burcheri 2013-04-22 07:27:07 UTC

I realized the error is not about ntp-client but was a failing dnsmasq for another reason:

$ rc-status 
Runlevel: default
 metalog                                [  started  ]
 dnsmasq                                [  stopped  ]
 netmount                               [  started  ]
 rsyncd                                 [  started  ]
 ntp-client                             [  stopped  ]
 fcron                                  [  started  ]
 cupsd                                  [  started  ]
 nfs                                    [  started  ]
 sshd                                   [  started  ]
 shorewall                              [  started  ]
 gpm                                    [  started  ]
 distccd                                [  started  ]
 vmware                                 [  started  ]
 xdm                                    [  started  ]
 local                                  [  started  ]
Dynamic Runlevel: hotplugged
 net.enp0s26f7u3                        [  started  ]
 net.enp0s25                            [  started  ]
Dynamic Runlevel: needed
 dbus                                   [  started  ]
 rpc.pipefs                             [  started  ]
 rpcbind                                [  started  ]
 rpc.idmapd                             [  started  ]
 rpc.statd                              [  started  ]
Dynamic Runlevel: manual

$ grep dnsmasq /var/log/everything/current 
Apr 22 11:05:55 [dnsmasq] unknown interface vmnet1
Apr 22 11:05:55 [dnsmasq] FAILED to start up

..that interface comes up later by some module.
Setting to INVALID...