Mailinglist Archive: opensuse (3336 mails)
| < Previous | Next > |
Re: [SLE] Updating the system clock
- From: Philipp Thomas <philipp.thomas@xxxxxxxxx>
- Date: Sat, 17 Dec 2005 07:05:47 +0100
- Message-id: <jv97q1t8q30t4v89s406d75ft6rc7rh23f@xxxxxxx>
On Fri, 16 Dec 2005 21:43:11 -0500, Paul W. Abrahams wrote:
>But nowhere in what I read did I find an explicit statement that ntpd
>queries the time servers once an hour to update the drift file,
Quoting from http://www.eecis.udel.edu/~mills/ntp/html/notes.html :
One of the things the NTP daemon does when it is first started is to
compute the error in the intrinsic frequency of the clock on the
computer it is running on. It usually takes about a day or so after
the daemon is started to compute a good estimate of this (and it
needs a good estimate to synchronize closely to its server). Once the
initial value is computed, it will change only by relatively small
amounts during the course of continued operation.
Nowhere in the documentation will you find an exact time like "one hour"
because there is no fixed frequency in which ntpd will update the drift
file.
Philipp
>But nowhere in what I read did I find an explicit statement that ntpd
>queries the time servers once an hour to update the drift file,
Quoting from http://www.eecis.udel.edu/~mills/ntp/html/notes.html :
One of the things the NTP daemon does when it is first started is to
compute the error in the intrinsic frequency of the clock on the
computer it is running on. It usually takes about a day or so after
the daemon is started to compute a good estimate of this (and it
needs a good estimate to synchronize closely to its server). Once the
initial value is computed, it will change only by relatively small
amounts during the course of continued operation.
Nowhere in the documentation will you find an exact time like "one hour"
because there is no fixed frequency in which ntpd will update the drift
file.
Philipp
| < Previous | Next > |