On Tue, Dec 01, 2015 at 12:00:51PM +0100, Holger Hoffstätte wrote:
> I haven't looked at the source yet, but it seems to me that loading and
> verifiying the configuration should not take several seconds before
> forking and returning. I don't have a ton of sources (2), they are all
> inhouse, healthy, reachable and DNS resolvable etc. So..any ideas?
Two things that by design delay the exit of the foreground process are
the -s option and the initstepslew directive. As you pointed out in
the bug this is useful to delay start of services that require the
system clock to be reasonably good from the moment they are started. A
different approach to wait until the clock is synchronized is to add a
separate chrony-wait service that just runs "chronyc waitsync".
Resolving of hostnames specified in the server/pool/peer directives
shouldn't add any delay, but hostnames in the allow/deny directives
do that.
Do you have allow/deny with a hostname in your config?
If the cause is something else, it's probably a bug that should be
fixed.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
