Re: Time Synchronizing Between Two Servers

illoai@xxxxxxxxx wrote:
[ ... ]
It may very well be noisier than just serving out ntp
to the local network, what with talk about elections
and such every 4 minutes, but generally everything
is kept within 0.050 seconds (and running ntpd on
all of the local machines feels like serious overkill).

Simply setting the date upon system boot and maybe once a day using cron to call ntpdate or whatever is probably good enough for any client machine, and OK for non-important servers where the exact timekeeping doesn't matter much.

ntpd is tiny by modern standards-- it's much smaller than a single Perl or Apache httpd+mod_Perl/PHP/whatever child process. :-) Normally, you choose your three (or more) most important servers, and run NTPd on them in a peer-aware ring with some external servers from the NTP pool, and then call ntpdate or run ntpd against only your local NTP resources for the rest of your machines.

Sun SPARC machines have good HW clocks, and also some of the newer Macs also seem to have consistently low values in ntp.drift and handle timekeeping well.

--
-Chuck

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Question about min/max poll and an interesting plot showing maxpolls effect
    ... Ntpd is supposed to set it's own polling interval; ... long poll intervals allow ntpd to correct small errors accurately". ... machines as clients of my stratum 1 server. ... The Ultra 5 is polling at 64 second intervals ...
    (comp.protocols.time.ntp)
  • Re: Question regarding loss of connection and ntpd not re-syncing the time.
    ... > of network connectivity; the ntpd daemon never re-syncs with its NTP ... If you are using DHCP on these machines and when you regain connectivity ... your DHCP server gives you another IP address you need to restart ntpd. ...
    (comp.protocols.time.ntp)
  • ntpd on FreeBSD
    ... After a power outaga, all our FreeBSD ... Nearly all of them had a problem though with ntpd. ... these machines booted before the the ntp servers came up. ... then restart ntpd. ...
    (freebsd-questions)
  • Re: NTP: time not synchronized
    ... we configure all others machines to synchronize on this time server. ... When I used monitor ntp, we can see that these machines have between 23 ... Large errors less that 1024 seconds can take a very long time to correct; the highest rate at which ntpd can slew the clock is 500 parts per million or about 43 seconds per day. ...
    (comp.protocols.time.ntp)
  • Re: ntpd on FreeBSD
    ... Nearly all of them had a problem though with ntpd. ... these machines booted before the the ntp servers came up. ... to the server when it starts, it will never sync. ... I can't see why you have two copies of ntpd running. ...
    (freebsd-questions)