Roger Oberholtzer wrote:
On Sat, 2011-07-16 at 10:35 +0200, Per Jessen wrote:
Per Jessen wrote:
If you need a higher degree of accuracy without a more accurate external time source, you have to improve the local time source - temperature controlled xtal oscillator etc.
btw, this is perfectly feasible. You can build/buy very stable TXCOs that will supply a very good PPS signal. Companies such www.rakon.com make very tiny devices with very good accuracies.
In our case, we are using high end GPS receivers with a PPS signal on the serial port. This causes a hardware interrupt when a time update is available. This is a rather accurate event when used in conjunction with a time setting daemon that can use the data and associated PPS signal from a GPS. In newer kernels, there is a PPS driver that has finally abstracted all these possible PPS signals into a single interface (/dev/pps).
That is understood, but I thought you had an issue with the GPS PPS signal being unavailable and the local clock not being sufficiently accurate.
And that question (still not answered) is: is there any unexpected side effect of not running the hwclock shutdown script?
I can't answer that - I think you'll have to google some more.
In my case, chrony wants to maintain the hardware clock between boots.
That makes sense, I'm sure I read somewhere that it's important that only one process maintain the hardware clock. -- Per Jessen, Zürich (17.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org