[EMAIL PROTECTED] writes:
> On Wed, Feb 01, 2006 at 07:25:35PM +0000, James wrote:
>> ntpq -p
>> remote refid st t when poll reach delay offset
>> jitter
>> ==============================================================================
>> ecoca.eed.usv.r 80.96.120.253 2 u 8 64 1 202.639 1436722
>> 0.001
This won't help the above problem but it might help the overall situation.
As I recall ntpd will not adjust the time above a certain threshold.
I don't recall the threshold but its pretty low.
I've found if I make ntp-client to run at boot time it sets the clock
before ntpd gets to it and makes sure its below that threshold. Once
the clock is below that threshold ntpd will keep it right (assuming
its connecting with time servers)
Throwing in my own question here. I'd never run ntpq -p before but
now I did and now wondering what a dash before severname means.
remote refid st t when poll reach delay offset jitter
==============================================================================
[...]
-atlas.jtan.com 128.4.40.12 3 u 488 1024 377 68.824 -11.85987.611
[...]
I couldn't find any reference to it in man ntpq which is loaded with
info.
It refers the reader like this:
For examples and usage, see the NTP Debugging Techniques page.
But doesn't bother saying what that is supposed to be a page of.
Also found this in there but its so cryptic I couldn't tell if this is
what I was looking for or what it shows a dash being used at least.
- outlyer
The peer is discarded by the clustering algorithm as an outlyer.
--
[email protected] mailing list
