On 2017-03-07 17:39, Per Jessen wrote:
Carlos E. R. wrote:
Suppose there is network, it hibernates, and on restore there is no network, the more complex situation. During hibernate the disciplined clock does not run; instead it reads the clock from the cmos on awake, which can be off by several seconds. But there being no network, it can't. When it gets a time, it will try to slew, which can take hours at best: typically the machine will hibernate again before it syncs.
Is that a problem? I mean, it's a laptop without permanent connection, how accurate does it need to be?
Not a need, a want. Sometimes I look at the computer to set a wall clock. Also, I want to be able to compare logs in two computers accurately. Mostly, I want to be able to know that the clock is good. I think the daemon can't work better in this situation that an hourly cronjob setting the time. Ie, use step instead of slew.
I also think that on some of those situations it bails off.
I can't believe it would do a good job.
In my experience it does a very good job. I have 2-3 laptops (12.3 and leap422) - they spend hours suspended or hibernation or just powered off. I've never noticed any problems.
No, you would have to compare the local time with an accurate clock. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))