sven falempin <sven.falem...@gmail.com> wrote: > Dear Tech reader, > > NTPD -S is useful, when a device is in storage for a while the clock is in > disarray. > But this assume the network exists, the fixed 15 seconds timeout makes > sense, > nevertheless it could be too long or too short. > > https://pastebin.com/gmNGpXLq > > Also NTPD just log out the failure after 15 seconds, not informing a script > that time is probably wrong. > > https://pastebin.com/z0eVrvgG > > 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 ?
No. It is a crappy workaround. I have schemed about a better method, but it is quite complicated and hasn't been written.
