Darren Salt wrote:
I demand that Florian Weimer may or may not have written...
Gradually skewing the clock doesn't exactly work that well if the offset
exceeds a few minutes. You don't want to run with a wrong clock for hours
or even days.
Maybe ntp, ntpdate etc. should recommend adjtimex?
If, then only ntpdate + adjtimex is a good combination.
ntp has its own sophisticated logic if skewing, but does not correct
offsets > 500 sec (AFAIK). Having your BIOS clock at local time (e.g.
UTC+1), then installing Linux with configuration system clock = UTC,
will remain a falseticker. Even offsets of some minutes need a long time
to be corrected by ntp.
Chrony can correct hours very fast.
Helmut Wollmersdorfer
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]