conf/129146: [rc.d] named and ntpd start order in rc.d

[John Marshall]

The following reply was made to PR conf/129146; it has been noted by GNATS.

From: John Marshall <john.marshall at riverwillow.com.au>
To: bug-followup at FreeBSD.org, nlandys at gmail.com
Cc:  
Subject: Re: conf/129146: [rc.d] named and ntpd start order in rc.d
Date: Fri, 28 Nov 2008 11:35:14 +1100

 --cNdxnHkX5QqsyA0e
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Nerius,
 
 Thank you for your report.
 
 The startup (rc) ordering of the named and ntpd components is correct.
 You have looked at the REQUIRE line in the ntpd script.  If you look at
 the REQUIRE line in the ntpdate script you will see that it requires
 named.  The way this works is that ntpd requires ntpdate which requires
 named.  You need to follow the chain back to get the picture.
 Dependencies in 7.0-RELEASE result in the following startup (rc) order
 (of pertinent components):
 
 /etc/rc.d/named
 /etc/rc.d/ntpdate
 /etc/rc.d/ntpd
 
 Perhaps you have a situation where the Internet is not available until
 after your system has started, so named is unable to resolve the
 hostnames for ntpd in time?  In such a case you are probably best either
 using IP addresses for servers in ntp.conf or re-starting ntpd later on
 (as you are doing).  In any case, your problem is not rc order but the
 inability of your named to resolve queries (for whatever reason) during
 startup.
 
 There is no problem with the rc order.  The order you desire already
 exists.
 
 I suggest that this PR can be closed.
 
 --=20
 John Marshall
 
 --cNdxnHkX5QqsyA0e
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.9 (FreeBSD)
 
 iEYEARECAAYFAkkvPMIACgkQw/tAaKKahKL5KQCffiKiNHyDMp6U/z3TNd002Ghq
 DgoAn32liwCRzcvakhxnXL2oYngmwVAY
 =ktSi
 -----END PGP SIGNATURE-----
 
 --cNdxnHkX5QqsyA0e--