On Sat, May 19, 2018 at 02:20:13PM +0000, aitor_czr wrote:

> > A small comment: Can you adjust your clock (again). Perhaps change the CMOS
> > battery? You are more than 1.5 hours ahead:(
> > Date:    Thu, 17 May 2018 23:54:39 +0000 (18/05/18 01:54:39)

>
> Yes, only 1.5 hours ahead!
>
> > What about installing ntpdate and run it with cron?
>
> Dear Svante, I significantly improved the behaviour of my random clock
> since, a year ago today, i decided to install ntpdate in all my computers,
> by the consensus of all the Veteran Unix Admins.
>
> I'm happy with the results, but sadly another factors come into play: the
> time interval during the click event..., the specified time interval for
> crontab... Currently i'm running ntpdate at every 40 miliseconds.

If cronned ntpdate is not enough, you really need one of ntp daemons
instead. Most of these are designed to handle such machines adequately.

The common wisdom is to avoid running ntpdate from cron completely.


Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Certified airhead; got the CT scan to prove that!
⠈⠳⣄⠀⠀⠀⠀