|[chrony-users] Delays before daemonizing|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
Peter Humphrey recently posted about his findings with an apprently
racy init script, see: https://bugs.gentoo.org/show_bug.cgi?id=566972
So far we've concluded that indeed the init script is inherently racy
due to accidental double-forking. I've since then investigated this a
bit more (see the bug) and wanted to ask for possible explanations why
chronyd's own daemonizing seems to take so surprisingly long before
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?
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.