On Wed, 29 Jan 2020 10:58:57 +0000 Rainer Weikusat via Dng <[email protected]> wrote:
> Dimitris via Dng <[email protected]> writes: > > On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote: > >> run ntpdate from > > > > i've witnessed cases in the past where ntpd wasn't time-syncing > > correctly, and ntpdate saved the date/time. > > so, IMHO, there's nothing wrong with ntpdate. > > There's nothing wrong with ntpdate provided there's nothing wrong with > having the wallclock make arbitrary backwards or forward jumps in > unpredictable intervals, IOW, if the only user is a human who doesn't > really care, everything's fine. Don't all time clients have an option to choose between all at once catch-up and slightly redefining a second so the catchup is more slow? Maybe ntpdate and that systemd thing also have such an option? SteveT Steve Litt January 2020 featured book: Troubleshooting: Just the Facts http://www.troubleshooters.com/tjust _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
