RE: [chrony-dev] makestep command sometimes makes chrony stop reading its sources |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: <chrony-dev@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-dev] makestep command sometimes makes chrony stop reading its sources
- From: "Hattink, Tjalling (FINT)" <T.Hattink@xxxxxxxx>
- Date: Thu, 21 Jan 2010 15:00:19 +0100
- Thread-index: AcqakyXIIJnVkPLCRb2rKJPzdr6TTwAC1TSQ
- Thread-topic: [chrony-dev] makestep command sometimes makes chrony stop reading its sources
>On Thu, Jan 21, 2010 at 12:46:30PM +0100, Hattink, Tjalling (FINT)
wrote:
>> I've applied the patch but when i executed makestep when the system
>> clock was one year in the past it made the offset twice as large (2
>> years in the past) and eventually chronyd freezed (100% cpu load)
>> after makestep was issued multiple times in a row.
>
>The freeze is probably worth investigating.
>
>
I've investigated it and it has actually nothing to do with makestep.
When I set the RTC clock 40 months back or forward in time, the chrony
daemon freezes as soon as it selects a reference clock. I think there is
an integer overflow somewhere.
--
Tjalling Hattink
---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.