Date: Tue, 15 Jul 2003 19:07:26 -0400 From: stan <stanb@panix.com> To: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> Cc: Free BSD Questions list <freebsd-questions@freebsd.org> Subject: Re: Seting the hardware clock Message-ID: <20030715230726.GB24083@teddy.fas.com> In-Reply-To: <44el0rpqlj.fsf@be-well.ilk.org> References: <20030714231604.GA27924@teddy.fas.com> <44oezw6kdk.fsf@be-well.ilk.org> <20030715133259.GA10641@teddy.fas.com> <44el0rpqlj.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 15, 2003 at 02:55:20PM -0400, Lowell Gilbert wrote: > stan <stanb@panix.com> writes: > > > 1. Set the hardware clock to some truly strange time (for testing > > software). > > > > 2. Reboot. > > > > a. time is set by the BIOS to the wrong time > > b. ntpdate corrects this (for the kernel). > > c. ntp keeps the time acurate (for this run session). > > > > 3. shutdown (BIOS time is not corrected). > > > > See the problem? > > Nope. ntpd is supposed to set the CMOS clock, and it certainly does > so for me. Interesting. It does not do this under Linux, and I was assuming that the behavior would be the same on FreeBSD. I expect that now that I know thta, I understnad what happened to me. On reboot with the CMOS clock set incorectly ntpd failed to satrt. I thien ran ntpdate by hand. But of course ntpd was no longer running to set the hardware clock. Thanks for making me think this thru. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715230726.GB24083>