Re: ntpd and cmos clock update

From: Dag-Erling Smørgrav (des_at_des.no)
Date: 08/30/05

  • Next message: M. Warner Losh: "Re: ntpd and cmos clock update" 
    To: "M. Warner Losh" <imp@bsdimp.com>
Date: Tue, 30 Aug 2005 15:36:45 +0200

    John-Mark Gurney <gurney_j@resnet.uoregon.edu> writes:
    > but since we don't set the TOD chip upon reboot, all the work that
    > ntpd did over the previous reboot is lost...

    echo 'ntpdate_enable="YES"' >>/etc/rc.conf

    DES 

    -- 
Dag-Erling Smørgrav - des@des.no
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
  • Next message: M. Warner Losh: "Re: ntpd and cmos clock update"

    Relevant Pages

    • Re: Clock skew changes drastically between reboots
      ... Every time I reboot the computer, the clock skew of the local ... For example, I boot the computer, let ntpd run for 12 hours, and the ... On some systems the TOD chip has the lowest frequency offset ...
      (comp.protocols.time.ntp)
    • Re: Sub-millisecond NTP synchronization for local network
      ... Chrony, as I understand it, is not so ... good at working over the internet. ... well as does ntpd. ... IF the frequency after reboot is very close to the frequency before (<1PPM ...
      (comp.protocols.time.ntp)
    • Re: F8 & F9: Date & Time
      ... >>> Yes, ntp is running and is properly, I believe. ... >>> after a reboot. ... remove ntpd from confusing issues on both F8 and F9 issue: ... verify time is right ...
      (Fedora)
    • Re: Very large offset and jitter values after reboot
      ... Strangely every time I reboot I get results like this, wich settle down after a while: ... ntpd will discipline the clock in the usual way. ... No drift file is better than one with an incorrect value for drift. ... the driftfile is being written to over a longer period of time and is used to correct a general drift of the clock. ...
      (comp.protocols.time.ntp)
    • Re: Very large offset and jitter values after reboot
      ... Strangely every time I reboot I get results like this, wich settle down after a while: ... ntpd will discipline the clock in the usual way. ... Even on a warm start with a good value in the drift file, ntpd can take up to thirty minutes to pull in to tight synchronization. ... ntpd uses some complex algorithms to discipline the clock. ...
      (comp.protocols.time.ntp)