| AW: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: AW: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements
- From: <thomas.schmid@xxxxxxxxx>
- Date: Wed, 31 Aug 2011 07:38:00 +0000
- Accept-language: de-CH, en-US
- Thread-index: AQHMZNfYruuXH1l/z0Gzkl/J+GmVDJUw96zv///51ICAAN19F4AB3paAgAJ/CbaAAEhUgIAAInaJ
- Thread-topic: AW: [chrony-users] Chronyd aborts when system time differs too much from chrony's measurements
Hi Miroslav,
> >.... I suspect one of the sourcestats asserts which check for
> >samples from future would fail here. Of course, chronyd should just
> >ignore an invalid dump and not crash.
>
> Can you do something about that ?
>Can you confirm it was the -s option that was causing the crash?
Aehm, I removed the "-r" option, and that prevented chronyd from crashing
system came up with an offset of 1 hour.
BTW: Did you get my email about the necessary additional CFLAGS to make RTC
access working with chrony 1.2.6 using Linux kernel 2.6.27.48 ?
Thomas Schmid
---
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.