11 Sep
2012
11 Sep
'12
6:15 p.m.
Am 11.09.2012 19:03, schrieb mike cloaked:
On Tue, Sep 11, 2012 at 5:52 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 11.09.2012 18:17, schrieb mike cloaked:
I guess you need to stop chrony when playing with hwclock. Maybe it is enough to just delete adjtime without that command.
Forgot to tell you (but it's probably too late now) to post the first line of your /etc/adjtime, this would have told us if we are on the right track.
OK I will try with chrony stopped - the first line of adjtime is:
0.000000 0 0.000000
I saved the file as .bak before fiddling!
Okay, that means your problem is NOT a broken adjtime. This basically says that your hardware clock does not drift.