Didier Kryn <[email protected]> writes: > Le 10/11/2015 01:01, Hendrik Boom a écrit :
[...] >> I used chrony as my NTP client. If the discrepancy between local time >> on the machine and the correct time, it just gave up. I/m not sure at >> what discrepancy this happened, but it helped a lot to explicitly set >> the time by my watch. Once the time was properly synced, though, >> chrony worked well to keep it correct. > > I use the package simply named "ntp" in Debian repo. [...] > This ntp client doesn't give up. That's not really true: The ntpd from the NTP reference implementation will raise a so-called 'clock panic' if the system time is off by more than the panic threshold (compile-time configurable as it seems) of 1000s. If the daemon was started with -g (Debian default), it will ignore the first panic and change the clock nevertheless. A subsequent one will cause it to exit. _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
