Carlos E. R. wrote:
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?
Typically it will be configured to use the local clock.
What if the machine suspends or hibernates?
Then it won't adjust any time :-)
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?
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. -- Per Jessen, Zürich (6.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org