| Re: [chrony-dev] "leapsectz" and leapsecond announce (was:refclock: Add a new "tai" option) |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] "leapsectz" and leapsecond announce (was:refclock: Add a new "tai" option)
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 12 Oct 2017 13:21:49 +0200
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com E024A3A26F
On Thu, Oct 12, 2017 at 11:31:13AM +0200, FUSTE Emmanuel wrote:
> One side question about "leapsectz" option: Does the use of the option
> imply ignoring leap announcements from other ntp servers or sources ?
> Which would imply that the timezone database MUST be maintained up to
> date to honor any future leap ?
>
> Or leap announcement is taken into account but utc-tai offset lost in
> case of a restart ?
>
> In any case, a little add to clarify this point would be great in the
> "leapsectz" option documentation.
Good questions. I'll add the following to the documentation:
The specified timezone is not used as an exclusive source of
information about leap seconds. If a majority of time sources
announce on the last day of June or December that a leap second
should be inserted or deleted, *chronyd* will accept it even if it
is not included in the timezone.
The TAI-UTC offset of the system clock will be wrong if the timezone
is missing a (genuine) leap second. If it is a fake leap second, the
clock will be twice (wrongly) corrected by one second.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.