|Re: [chrony-users] Two Issues|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Thu, Mar 12, 2015 at 07:18:26AM -0400, Weary1 wrote:
> >>Weeeeellll... There is one other complicating factor, which *MAY* have had
> >>a hand in the server's System Clock getting so far out of whack, and which I
> >>didn't mention earlier:
> >How it happened does not really matter. It happened. use the initstepslew
> >directive in chrony.conf to have it step the clock if it is initially too far
> That will require a restart of chrony, after I change chrony.conf. I'll get
> to that after dealing with these messages.
Please note that the initstepslew directive works only with sources
that are available/resolvable when chronyd is started. It is mainly
useful when chronyd should block boot until the clock is set. Usually
it's better to use the makestep directive in chrony.conf, which works
with all sources.
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.