Re: [chrony-users] time.google.com crash chronyd

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

Just to amplify what I said, here is a link to google's page
https://developers.google.com/time/smear
They use a one day smear rather than the one hour smear I suggested in my
response.

Note that this should ONLY be a problem around a leapsecond, and there has
been no leapsecond for a while (Dec 31,2016 was the last one), so it is highly doubtful that the OP's
problems with time.google.com originated from this smearing of the time around
a leapsecond.

On Sun, 6 May 2018, Alvaro G. M. wrote:

> On Sun, May 06, 2018 at 01:54:31PM +0200, Nicolas Embriz wrote:
> > For an unknown reasons when using time.google.com chronyd don’t stat but if
> > I use for example “time.apple.com” it works, this is the output I get when
> > using chronyd -d:
>
> I can't help you with that, but I think you should be aware that
> time.google.com behaviour is non standard, so you may not want to use it.
>
> https://github.com/systemd/systemd/issues/437
>
> (You can ignore all the systemd flame, just the main post is enough and has
> the references you may need to further investigate this thing).
>
> Best luck!
>
> --
> Alvaro G. M.
>
> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.