Matthew Burgess wrote:
I think the solution is to move the initial time-sync operation out of the bootscript and into the configuration section of NTP (obviously with enough explanation as to why we need to do this and why it should be a one-time operation, but faulty hardware like a dodgy CMOS battery might require it to be rerun). This should avoid the problem of the clocks being too far out that ntpd refuses to sync them. It then allows `ntpd' to start up nice and quickly during the boot process as it operates in its normal gradual adjustment mode.
The fly in the ointment here is if you're unfortunate enough to share you computer with someone who likes to boot into windows. Windows likes to reset the system clock to local time which can be hours different to UTC. Ntp then quits without trying to correct it as the difference is too large. For those unfortunate souls, the ntp -g option may be the best compromise -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
