31 Mar
2018
31 Mar
'18
1:23 p.m.
On Saturday 31 March 2018 05:08:12 Rolf Schmidt wrote:
Hi,
I did find one reference to about 1.1 hours between updates. I'd assume,
having dealt with this before when mobo clocks weren't so accurate,
(I've had a linux only house since 1998) ntp claimed to adjust this
interval, and later to adjust the clock's drift so it eventually settled
to a very small error and the update rate would fall back to the
default. No idea if this is still true, and the man pages seem to have
been eviscerated of such info. Sad state of affairs IMNSHO.
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
The additional info is that logging out and
logging back in -- which
is something I rarely do; I often go weeks without doing so, but I
happened to do it today -- "fixed" the problem.
It seems that your clock will set at login time perhaps you set/use
different timezones for the clocks.
I usually use ntpd to sync my clock via internet. But make shure your
clock has less then 1 or 2 minute differenc to utc.
Best is:
- stop the ntp daemon
- use ntpdate to correct you clock
- perhaps use 'hwclock -w' to adjust the hardware clock too.
- start ntpd again.
Now the clock will be adjusted continusly (I don't know the length of
the intevall between two updates).
HTH
Rolf