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
msg52514/pgp00000.pgp
Description: PGP signature
