Prev: no sound on my hp dv7 notebook using alsa
Next: ntpd still not working
From: root on 1 Nov 2009 22:00
How long does it take for the daemon to fix the
clock drift? The daemon has been running for
9 hours and my clock is off by 6 minutes. Without
ntpd my clock would have been off by roughly the
same amount.
From: jim dorey on 2 Nov 2009 00:45
root wrote:
> How long does it take for the daemon to fix the
> clock drift? The daemon has been running for
> 9 hours and my clock is off by 6 minutes. Without
> ntpd my clock would have been off by roughly the
> same amount.

if you gotta, run ntpdate before starting ntpd...i've got ntpdate in a
cron job set for daily, i get a drift of a few seconds a day, i'm not
hyper critical on that, like i used to be.
From: root on 2 Nov 2009 01:06
jim dorey <skaar(a)ns.sympatico.ca> wrote:
> root wrote:
>> How long does it take for the daemon to fix the
>> clock drift? The daemon has been running for
>> 9 hours and my clock is off by 6 minutes. Without
>> ntpd my clock would have been off by roughly the
>> same amount.
>
> if you gotta, run ntpdate before starting ntpd...i've got ntpdate in a
> cron job set for daily, i get a drift of a few seconds a day, i'm not
> hyper critical on that, like i used to be.

I did run ntpdate just before I started ntpd. Nine hours later
the entry in /etc/ntp/drift was still 0.000. When does it get
changed?
From: Henrik Carlqvist on 2 Nov 2009 02:13
root <NoEMail(a)home.org> wrote:
> How long does it take for the daemon to fix the
> clock drift? The daemon has been running for
> 9 hours and my clock is off by 6 minutes. Without
> ntpd my clock would have been off by roughly the
> same amount.

If so it seems as if ntpd hasn't succeeded in keeping your clock
synchronized. What output do you get from ntptrace?

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: root on 2 Nov 2009 05:44
Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
> root <NoEMail(a)home.org> wrote:
>> How long does it take for the daemon to fix the
>> clock drift? The daemon has been running for
>> 9 hours and my clock is off by 6 minutes. Without
>> ntpd my clock would have been off by roughly the
>> same amount.
>
> If so it seems as if ntpd hasn't succeeded in keeping your clock
> synchronized. What output do you get from ntptrace?
>
> regards Henrik

I just re-started ntpd, after deciding it wasn't helping.
After a few seconds of operation ntptrace yields:
localhost: stratum 16, offset 0.000000, synch distance 0.000210

I don't have a man entry for ntptrace, what should I be looking
for?
 |  Next  |  Last
Pages: 1 2 3 4
Prev: no sound on my hp dv7 notebook using alsa
Next: ntpd still not working