On Tue, Aug 21, 2012 at 10:53:31AM +0100, Tomalak Geret'kal wrote: > On 21/08/2012 10:24, Miroslav Lichvar wrote: > >There are some other areas which needs update, for instance the > >section with server name resolving on start is no longer valid, as > >chrony will try it later after start. > That's interesting actually as when I put NTP servers "ntp1" "ntp2" > "ntp3" (which don't exist) as sources, chrony 1.26 startup takes an > age as if it's trying to resolve the hosts and eventually timing > out, before daemonisation!
Unfortunately the resolving is still blocking, eventually I'd like to use an async DNS library or do it in a thread. In 1.27-pre1 the first resolving was moved after the daemonisation though. -- 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.
