Subject: Re: rc.d: time synchronization issues at boot time
To: None <>
From: Luke Mewburn <>
List: tech-userlevel
Date: 03/16/2005 21:51:01
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:
  | >=20
  | > 	server
  | > 	server
  | > 	server
  | 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 ?

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.6 (NetBSD)