|[chrony-users] AW: chronyc: Update by "trimrtc" not refelected in rtcfile ?|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
- To: <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: [chrony-users] AW: chronyc: Update by "trimrtc" not refelected in rtcfile ?
- From: <thomas.schmid@xxxxxxxxx>
- Date: Wed, 14 Sep 2011 13:30:17 +0000
- Accept-language: de-CH, en-US
- Thread-index: Acxy1MaeMnVPZxRbRSSwlZO92YCkMQAAJv3AAAMf1LA=
- Thread-topic: chronyc: Update by "trimrtc" not refelected in rtcfile ?
> -----Ursprüngliche Nachricht-----
> Von: Listengine [mailto:listengine@xxxxxxxxxxxxxxxxx] Im Auftrag von
> Gesendet: Mittwoch, 14. September 2011 13:59
> An: chrony-users@xxxxxxxxxxxxxxxxxxxx
> Betreff: [chrony-users] AW: chronyc: Update by "trimrtc" not refelected
> in rtcfile ?
> > The result was that the system time was abruptly corrected by 3608s
> > into the future,
> > which of crashed my special application.
> > Don't I use trimrtc correctly ? Did I miss something ?
> It does this even when I perform the same steps manually in chronyc:
> 1. issue "password <pw>"
> 2. issue "trimrtc"
> 3. wait 5s
> 4. issue "writertc"
> 5. Stop chronyd by SIGTERM
I found a possible, but really ugly hackish workaround: After the RTC
files has been written ("trimrtc") and chronyd has been terminated, I
set the 3rd parameter in /etc/chrony.rtc (offset) to "0.0". When chronyd
starts again (chronyd -s) I have the benefit of the RTC drift data,
but the system time is not falsely adjusted by the offset in the RTC file.
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.