On Tue, Nov 10, 2015 at 05:01:41PM +0000, Rainer Weikusat wrote: > Didier Kryn <k...@in2p3.fr> 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.
I remember the clock was more than an hour out. Possibly more than a day. Perhaps chrony also has a clock panic. -- hendrik _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
