Subject: Re: rc.d: time synchronization issues at boot time
To: None <tech-userlevel@NetBSD.org>
From: Luke Mewburn <lukem@NetBSD.org>
Date: 03/16/2005 21:51:01
Content-Type: text/plain; charset=us-ascii
On Wed, Mar 16, 2005 at 10:24:20AM +0000, Alistair Crooks wrote:
| On Wed, Mar 16, 2005 at 12:28:46PM +1100, Simon Burge wrote:
| > Especially since our default ntp.conf lists names that need to be
| > resolved:
| > server 0.pool.ntp.org
| > server 1.pool.ntp.org
| > server 2.pool.ntp.org
| Exactly - and this is where we have the chicken and egg problem.
| named requires "good time", presumably for TTLs (and I would think
| that kdc would need this too), and to get that, we need to go to
| a time server and find out what the "good time" is. But we can
| only do that when we've resolved the name of the time server.
Can anyone confirm if named will not barf if ntpdate starts after
named and ntpdate skews the time ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
-----END PGP SIGNATURE-----