sven falempin [sven.falem...@gmail.com] wrote: > > Alast why not just wait for something to respond and then set time ?? > This (bit ugly) diff reveals some dead code in ntpd > > https://pastebin.com/9PwqBDHz > > Is there another way to bootstrap time correctly ? >
ntpd will wait under normal invocation, but -s jumps the system time and ntpd is only given the limited amount of time for this to happen. The system does not want to jump to a new time once other daemons are started. That's why the behavior is the way it is now. If you know you have an interface that takes a long time to come up for some reason, you can add an appropriate 'sleep' statement in the hostname.if file, or even a script that takes on a more complicated set of actions before allowing the system to move forward.
