Roger Oberholtzer wrote:
We have a system that is booted every day. We use gpsd to monitor a GPS receiver. We had issues with ntp in this setup. So, we instead use chrony. It works great in a system that is booted and where the time may be off significantly.
Unlike ntpd, chrony can be told to to a brute force time change when it first gets a time. After that time changes are more gradual.
Doesn't "ntpd -g" do exactly that ?
Your source of time will be on the network. So maybe that will also be an issue for chrony. But I would suggest you give it a shot. If only because it works much better with systems that are continuously restarted and may be off from the correct time by a significant amount.
I'm surprised ntpd doesn't work in the setting too, but although I use it on my laptop, I've never noticed if it misbehaves when there is no network. -- Per Jessen, Zürich (0.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org