On Thursday 15 December 2005 4:32 am, Per Jessen wrote:
"During operation ntpd measures and corrects for incidental clock frequency error and writes the current value to a file called by default /etc/ntp.drift"
My reading of the online description of ntp seems to indicate that the drift file is updated hourly, but when I did an ls on it I found that it hadn't been modified for over a day. And the only place I could find a file named ntp.drift was in /var/lib/ntp/drift/ntp.drift rather than the expected /etc/drift/ntp.drift Maybe I'm misunderstanding the udel description of ntpd, but I thought from that description that the external servers are contacted hourly, and that on each such occasion (a) the hardware clock is set to the time gotten from the external servers, and (b) the drift file is updated. Though come to think of it, if that's what happens then the drift file is useless. So after attempting to understand the ntpd description, I still have several questions: 1. How often are the external servers consulted? 2. What happens when they are consulted? 3. How often is the drift file updated? 4. When and how is the data in the drift file used? Anyone know?
what does "ntptrace" say? It sounds more like your clock isn't in fact being synchronised.
It says: suillus:~ # ntptrace /usr/sbin/ntpq: read: Connection refused Paul