[chrony-users] Intermittent network access even at boot

["Wickham, Mark" <Mark.Wickham@xxxxxxxx>]

Hello,

 

I am working on a line of Linux products that have an RTC with no battery, so it returns to Jan 1970 every time it is powered off/on.  After attempting to use openntpd for a while, we see that Chrony is a much better fit.  Our device may run without network for long times, even at boot time, and so we need some way for the device to start up, and get time later.

 

Hanging within the startup scripts is not acceptable because we have other daemons that also need to be started, whether or not we have a network.

 

The README indicates that if DNS is not available at startup, it will not be consulted later.  Is this still the case?

 

Do you have any patches or suggestions for making Chrony capable of running in a truly intermittent network environment?

Thanks in advance for any help.

 

Mark Wickham
Senior Principal Software Engineer

Digi International^®
11001 Bren Road E

Minnetonka, MN 55343

Direct: 952 912 3353

Main: 952 912 3444

Email: Mark.Wickham@xxxxxxxx

www.digi.com