Date: Sun, 16 Feb 2003 18:05:53 -0800 From: Kris Kennaway <kris@obsecurity.org> To: current@FreeBSD.org Cc: phk@FreeBSD.org Subject: Clock disabled during DDB Message-ID: <20030217020553.GA67649@rot13.obsecurity.org>
index | next in thread | raw e-mail
[-- Attachment #1 --] Is it an expected feature that the system clock is not updated when the system is sitting in DDB? I just had 8 machines sitting in DDB for about 20 minutes at boot (because of that &^@%&^ sysctl LOR), and ntpd refused to time-sync them when I continued, because the clock had fallen too far behind: Feb 16 17:18:08 <ntp.err> gohan12 ntpd[177]: time correction of 1149 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Feb 16 17:18:12 <ntp.err> gohan10 ntpd[177]: time correction of 1155 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Feb 16 17:18:00 <ntp.err> gohan15 ntpd[177]: time correction of 1169 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. ... Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+UEOBWry0BWjoQKURAli0AJ9liml7g6rDJ39VxJH4mqIRekfcjwCg0bYr dAxNVyWCqNv/ggFb1lWcG80= =Muax -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030217020553.GA67649>