Miroslav wrote:
> A leap-smearing server suppresses the leap second bits in its
> responses, but it could happen if the client knew from other time
> sources or tzdata (enabled by leapsectz) that there was a leap second.
So before using a new NTP service, it's needed to do some research.
Or does
William G. Unruh wrote:
> Yes. That was why Miroslav said it should be the user machine's responsibility
> to smear, not the server's. The server should deliver UTC, and UTC has leap
> seconds
> (ie 23:59:58 goes to 00:00:00 or 23:59:59 goes to 25:59:60 and then to
> 00:00:00.)
> AFAIK there is
Hey Holger,
Holger wrote:
> an important point for you since you're presumably in Germany and
Jawoll, under protection of CoronaSchVO NW.
> I already went through the futile attempts to use these servers:
> they're all outside Germany, with rather high latency and quite
> terrible connectivity,
Miroslav wrote:
> On Wed, Apr 08, 2020 at 02:16:23PM +0200, Lars-Daniel Weber wrote:
>
> > On the manfile to chrony.conf there's also this as a recommendation:
> > > leapsecmode slew
> > > maxslewrate 1000
> > > smoothtime 400 0.001 leaponly
>
&
Holger wrote:
> It's really just a cleaned up default (template) config..
On the manfile to chrony.conf there's also this as a recommendation:
> leapsecmode slew
> maxslewrate 1000
> smoothtime 400 0.001 leaponly
https://chrony.tuxfamily.org/doc/3.4/chrony.conf.html
I'll give it a try.
--
