--sL7C0a98p/u5aVah
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          0.pool.ntp.org
  | > 	server          1.pool.ntp.org
  | > 	server          2.pool.ntp.org
  |=20
  | 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 ?

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFCOA+VpBhtmn8zJHIRAnkzAJ4jqJPo3DDBBSmwo3c8zrtiTSobSACfcJKz
pk8VU6x3ux4D/ISIC73/3Qg=
=nM6Y
-----END PGP SIGNATURE-----

--sL7C0a98p/u5aVah--