Patrick Nolan wrote:
> I'm having trouble with one linux client out of a group.
> It seems as if ntpd can't keep its clock syncronized. It's
> drifting about 6-10 minutes per day, well over the 500 ppm limit.
Could it be that "clock spread spectrum" is
enabled (in bios) on that box and
not on any
Steve Kostecke wrote:
> On 2007-10-20, Jos van de Ven <[EMAIL PROTECTED]> wrote:
>>so my system clock runs too fast due to 1000 Hz setting as I
>>understand. I read that -148 ppm is not a good clock; should be no
>>more than absolute 50 ppm.
>
>
> That's simply not true.
>
> ntpd is able to app
>The only "trick" around this, is to use a TCP-based VPN tunnel to a
>point outside the firewall, and forward your queries through this.
>However, a "solution" like this will add a VARIABLE latency on your
>packets, giving you (in reality) a worse clock than using the internal
>CMOS one.
A ntp se
>A bad clock frequency is a hardware issue!
Or a software bug. There have been troubles with roundoff
on the value of the tick size.
--
These are my opinions, not necessarily my employer's. I hate spam.
___
questions mailing list
questions@lists.ntp
On 2007-10-20, Jos van de Ven <[EMAIL PROTECTED]> wrote:
> My relative frequency is stable at about -148 ppm,
That number is the frequency CORRECTION applied by ntpd.
The fact this this value is stable is much more important than the value
itsself.
> so my system clock runs too fast due to 1000
"Jos van de Ven" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
[...]
> My relative frequency is stable at about -148 ppm, so my system clock
> runs too fast due to 1000 Hz setting as I understand.
It would run fast if not corrected, but I would hesitate to ascribe it
to the kernel's
After OP posted the start of this thread, I wanted to know more about this,
but as I dig deeper it becomes more confusing to me.
My server runs fine (I think) on a 2.6.9- kernel. I read that 2.6 kernels
have 1000 Hz as default and you can not change that in config files. At
least I don't see an
Patrick Nolan wrote:
> On 2007-10-19, Richard B. Gilbert <[EMAIL PROTECTED]> wrote:
>>Check the value of a Kernel variable called "HERTZ". Some Linux systems
>>set it to 1000 which is not good for NTP. If yours is set to 1000 (or
>>250) try changing it to 100.
>
>
> More ignorance on my part
In article <[EMAIL PROTECTED]>,
lmr <[EMAIL PROTECTED]> wrote:
> Is xntpd configurable to reconnect if the connection fails?
xntpd is either seriously obsolete or misnamed.
No version of ntpd uses connection oriented protocols, so there are no
connections to fail. See the very recent thread abo
In article <[EMAIL PROTECTED]>,
Harlan Stenn <[EMAIL PROTECTED]> wrote:
>>> In article <[EMAIL PROTECTED]>, Patrick Nolan <[EMAIL PROTECTED]> writes:
Patrick> 6-10 minutes per day, well over the 500 ppm limit.
> As others have noted, ntpd cannot help in this situation, if it cannot be
If it is
10 matches
Mail list logo
