It's a code analysis tool which looks for software bugs.
Regards,
--
-Chuck
Does NTPD_TICKADJ_PPM allow the use of clocks which are more than 500 ppm
out? Sorry if I missed any earlier discussion on this (and I don't run
Linux). How does one go about determining the value to set - just
guesswork?
I'm interested because someone has just reported problems with NTP on a
system which gain (or loses) 1 second in 10 minutes! 1 part on 600! This
adjustment could be most helpful.
Thanks,
David
Thanks for your thoughts, Bill. No, this is a real PC, which used to work
correctly. There is a question as to (a) whether the PC has become
faulty, (b) whether something had changed in the software, or (c) whether
some other program is interfering with the time. Nothing is supposed to
have changed in the software, and there are no restore points early enough
to check (b). The obvious candidates for (c) are not present, which
leaves (a) as the obvious cause, but I has my doubts that a PC would
suddenly start to lose 1 second every ten minutes.
I don't know whether the loss is constant, as with NTP running it keeps
resetting, and investigations are continuing. It's at the point where I'm
running out of ideas, so I may, very reluctantly, ask Dave H to get
involved, if the current tests prove unsuccessful. These tests are now to
try and run as plain an NTP as possible, but a more recent version
(4.2.6p4). I'll post the outcome here.
Cheers,
David
No way. ntpd will not reset the clock. If it finds the rate that far
out, it will shut down.
> resetting, and investigations are continuing. It's at the point where I'm
> running out of ideas, so I may, very reluctantly, ask Dave H to get
> involved, if the current tests prove unsuccessful. These tests are now to
> try and run as plain an NTP as possible, but a more recent version
> (4.2.6p4). I'll post the outcome here.
The question is whether or not it is consistant, in which case it sounds
like the system is not setting the intial clock rate properly. The
system has an internal crystal, and a timer chip which counts a certain
number of oscillations and interrupts. It also calibrates the cpu
counter against the timer ticks. Now it is hard to imagine how that
hardware would go wrong.
a)find out if the time rate loss is consistant.
b) Try running chrony instead of ntpd and find out what the rate
correction is and see if it is consistant.
>
> Cheers,
> David
>