Date: 26 Apr 2003 13:03:47 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-questions@freebsd.org Subject: Re: Time Problem in 5.0 Message-ID: <447k9hnqbw.fsf@be-well.ilk.org> In-Reply-To: <87of2t8f3a.fsf@pooh.honeypot.net> References: <20030424214413.GC90097@grimoire.chen.org.nz> <20030425091950.GA558@dhumketu.homeunix.net> <3EA92FF1.30809@potentialtech.com> <20030425184813.GA674@dhumketu.homeunix.net> <448ytye5xj.fsf@be-well.ilk.org> <3EA9925E.30201@potentialtech.com> <20030425203301.GU45035@dan.emsphone.com> <3EA9D2EC.3040304@potentialtech.com> <20030426010835.GB5143@dan.emsphone.com> <3EA9EDF4.9000702@potentialtech.com> <20030426024616.GF5143@dan.emsphone.com> <87of2t8f3a.fsf@pooh.honeypot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Kirk Strauser <kirk@strauser.com> writes: > At 2003-04-26T02:46:16Z, Dan Nelson <dnelson@allantgroup.com> writes: > > > But ntpdate does serve a useful purpose during bootup. > > Dan, something I've always wondered about: if a machine runs ntpd during > normal operation and is rebooted mainly for periodic maintenance, wouldn't > it's hardware clock be accurate to within a few fractions of a second during > the downtime? I mean, if my clock it NTP-correct at noon, and I reboot the > machine to do a `make installworld', it will be pretty close to accurate > when I bring it back online. Since ntpd launches instantly when not in `-q' > mode, what's the advantage or point of running ntpdate on boot? Why not > just start ntpd as normal and let it smooth over the small amount of drift? Yep. For cases where the drift isn't small, though, it's important. Some examples: machines without a working real-time clock, dual-boot machines that have had the time adjusted incorrectly by another operating system, machines where the real-time clock had been stepped on in the last boot...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447k9hnqbw.fsf>