| Re: [chrony-dev] makestep command sometimes makes chrony stop reading its sources |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Wed, 20 Jan 2010, Miroslav Lichvar wrote:
On Wed, Jan 20, 2010 at 08:41:53AM -0800, Bill Unruh wrote:
On Wed, 20 Jan 2010, Hattink, Tjalling (FINT) wrote:
I've looked into the initstepslew command but I think it only works for
NTP
sources, and I only have a reference clock available (SHM, PPS). Also
I am not sure about that-- ie that the initstepslew is only available for
network sources. I will have to look at the source code.
It works only for NTP sources, it's the acquire module which
duplicates a lot of the NTP code from ntp_* modules.
I was thinking about implementing an option that would allow chronyd
to step the clock when a threshold is reached. Maybe only a
configurable number of times, to mimic the -g option which ntpd has.
This would work for any sources.
As long as it is an option, and not built in as it is for ntp. I have never
figured out why ntp, which acts like a fussy grandmother and disallows all
rates greater than 500PPM away from the nominal, then goes ahead and
institutes compulsory steps when the clock is off by 1/8 of a sec. (ie an
infinite rate adjust).
And add an option for NTP sources to make a burst on start and thus
make the initstepslew command obsolete.
I think keeping the initstepslew is still a good idea. I use it for example
from a time source that in general is a lousy time source, but I know is going
to be reachable, just in order to make sure that the clock is within some
reasonable range of right at startup. Thereafter I do not want to use that
source, because I know it is lousy.
One can of course use chronyc to do a burst ( which does not however step the
clock).
---
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.