On 2017-03-07 14:43, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-03-07 14:00, Mathias Homann wrote:
Am Dienstag, 7. März 2017, 03:45:40 CET schrieb Carlos E. R.:
No, running the ntpd daemon is not an option here.
...why? just wondering.
Because the laptop is not always connected to internet.
You can still run ntpd. It does not require a permanent connection.
I'm unsure of that. What does it do when the connection dies? What if the machine suspends or hibernates? 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. I also think that on some of those situations it bails off. I can't believe it would do a good job. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))