Re: ntpd and cmos clock update

From: Dmitry Mityugov (dmitry.mityugov_at_gmail.com)
Date: 08/29/05

  • Next message: David Malone: "Re: bge driver internal routing issues?"
    Date: Mon, 29 Aug 2005 16:20:56 +0400
    To: freebsd-hackers@freebsd.org
    
    

    On 8/28/05, Andriy Gapon <avg@icyb.net.ua> wrote:
    >
    > I think I saw more than once speculations that FreeBSD updates CMOS
    > clock when time is set, so CMOS clock value should always be very close
    > to internal OS timer. But I always took it with a grain of salt because
    > every time I reboot after long uptime period I see messages from ntpd
    > about adjusting clock by many seconds and such discrepancy should not
    > occur, of course, during couple of minutes that reboot takes.
    ...

    That's why I always thought that ntpd did not work in FreeBSD 5.x!

    -- 
    Dmitry Mityugov, St. Petersburg, Russia
    I ignore all messages with confidentiality statements
    "We live less by imagination than despite it" - Rockwell Kent, "N by E"
    _______________________________________________
    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: David Malone: "Re: bge driver internal routing issues?"

    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: 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)
    • Re: Preventing ntpd from adjusting time (backwards)
      ... it's possible to make ntpd *not* adjust the time. ... This seems to be a bete-noir for the dovecot developer. ... backwards on each reboot, and then dovecot does it's dying swan thing. ... the step threshold, the clock is stepped immediately, ...
      (freebsd-questions)
    • Re: ntpdate
      ... >> changing the time while ntpd is running is bad, it will just mess with what ... >> the daemon is doing. ... if the clock is wrong ntpd should already be taking ... > not going to reboot them just to test this. ...
      (comp.os.linux.security)