| Re: Aw: Re: [chrony-users] How to use Facebook's NTP-service correctly? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: Aw: Re: [chrony-users] How to use Facebook's NTP-service correctly?
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 7 Apr 2020 19:55:13 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586282120; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3ubRsGQSKMTUgLnSw21AOC6ejGT24LtlWUO94vSXcrM=; b=I81IcSJwkR2m3bAxI+ueBJrcPchlqdl9+axaB7Ab8lX3ZUIfUJcpqUpPEfVRIwoEKBBWMn +OJEWs9D/sbkGAyw4MOEpcd9hsi1YGgIBkJ1p/18zZVPt3CQ5PKewegoUrJuaRWwzQu0yN QrDrFk8ffY6YrUON662tc+KDgFNv+UQ=
On Tue, Apr 07, 2020 at 10:43:51AM -0700, Bill Unruh wrote:
> Would not using a smeared source for chrony which has implimented smearing
> just result in "double smearing" as chrony expects a step discontinuity and
> never gets it?
> So before 00:00:00 chrony would speed up the clock iand then discovered
> that no step arrived at 00:00:00 and find itself 1 sec
> out from its source?
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.
--
Miroslav Lichvar
--
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.