| Re: AW: [chrony-users] chrony: Use of RTC trimming together with ntpdate: A Bad Thing ? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Wed, Aug 31, 2011 at 07:11:09AM +0000, thomas.schmid@xxxxxxxxx wrote:
> I understand, but as this happens during bootup, I *need* a way to find out when chronyd's
> "initistepslew" has finished, to allow me to remove the temporary route to the NTP server
> (in reality it is a temporary default route).
> So the chrony startup script has run, chronyd was started and the bootup continues to start
> more services on the system. And I *need* to have this temporary route removed *before*
> the routing services of my system are started in the bootup.
> Right now I don't see how I could pick the right moment to remove the route; chronyc cannot
> be run (no terminal) and I don't want to rely on looking for clues in syslog.
With the latest code in git the foreground process exits after
initstepslew (and other initialization) is completed, successfully or
unsuccessfully.
Why do you need a terminal to run chronyc?
--
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.