| Re: [chrony-users] New with 1.30: stuck after resume from suspend |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Thu, Jul 03, 2014 at 04:53:00PM +0200, Holger Hoffstätte wrote:
> On 07/03/14 16:33, Miroslav Lichvar wrote:
> > There is a difference in how are the scheduled timers corrected when
> > chronyd reaches a timeout (select() returning 0) and when an
> > external request (e.g. chronyc command) wakes it up.
> >
> > When it doesn't timeout, all scheduled timers are moved by the
> > interval between last select() call and the current time. This means
> > if a chronyc command is issued before chronyd timeouts, the actual
> > time it takes to send first request after suspend could be up to
> > 2*maxpoll.
>
> Oh! That might explain why I didn't observe it sooner and kicked it.
FWIW, with the latest code in git, when select() modifies the timeout
value (e.g. on Linux), the scheduled timers should be always moved
only by the amount of time for which was the system suspended.
--
Miroslav Lichvar
--
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.