Bug#974845: chrony: Add leapsecond info

2020-11-15 Thread Kurt Roeckx
On Sun, Nov 15, 2020 at 07:25:59PM +0100, Vincent Blut wrote:
> Hi Kurt,
> 
> On 2020-11-15T14:29+0100, Kurt Roeckx wrote:
> > Package: chrony
> > Version: 4.0-2
> > Severity: wishlist
> > 
> > Hi,
> > 
> > Could you please add the following line to the default chrony.conf
> > file:
> > leapsectz right/UTC
> 
> Funnily enough, I am working to make the fragmentation of the chronyd
> configuration easier. To make sure it works as it should, I wrote an
> autopkgtest [1] that adds (you guessed it!) "leapsectz right/UTC" to the
> chronyd configuration using a fragment in /etc/chrony/conf.d.
> 
> As to set "leapsectz right/UTC" by default, it's something I've been
> planning to do for some time, but I always step back knowing that this will
> cause problems for users of leap smearing servers [2] and those who

By default, we use servers from the pool. As far as I know,
servers from the pool should not be smearing. The default of
chrony itself is also to use a step (leapsecmode system).

> don't update their systems and find themselves with an obsolete version of
> tzdata (nothing I can do here though).

An obsolete version of tzdata is actually not a problem. From the
manpage:
| 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, it will be accepted even if it is
| not included in the timezone.

Having the settings just makes sure that you get leap second
announcement and hopefully propagate it to your clients.

> [1] 
> https://salsa.debian.org/debian/chrony/-/commit/3124fb4c8ec547b5a1e606ccb8d02906166960e3
> [2] Notably the Debian Cloud Team that configured chrony (used by default)
> to use the Amazon Time Sync Service for EC2 and the internal NTP server
> provided by Google (metadata.google.internal) for the GCE images. Both serve
> leap-smeared time.

So they already changed the default to use different servers. If
those servers are smearing servers, it just means they need to
change something else in their config file.


Kurt



Bug#974845: chrony: Add leapsecond info

2020-11-15 Thread Vincent Blut

Hi Kurt,

On 2020-11-15T14:29+0100, Kurt Roeckx wrote:

Package: chrony
Version: 4.0-2
Severity: wishlist

Hi,

Could you please add the following line to the default chrony.conf
file:
leapsectz right/UTC


Funnily enough, I am working to make the fragmentation of the chronyd 
configuration easier. To make sure it works as it should, I wrote an 
autopkgtest [1] that adds (you guessed it!) "leapsectz right/UTC" to the 
chronyd configuration using a fragment in /etc/chrony/conf.d.


As to set "leapsectz right/UTC" by default, it's something I've been 
planning to do for some time, but I always step back knowing that this 
will cause problems for users of leap smearing servers [2] and those who
don't update their systems and find themselves with an obsolete version 
of tzdata (nothing I can do here though).



And add a Depends on tzdata, so that the timezone info is
available.


[…]


Kurt


Cheers,
Vincent

[1] 
https://salsa.debian.org/debian/chrony/-/commit/3124fb4c8ec547b5a1e606ccb8d02906166960e3
[2] Notably the Debian Cloud Team that configured chrony (used by 
default) to use the Amazon Time Sync Service for EC2 and the internal 
NTP server provided by Google (metadata.google.internal) for the GCE 
images. Both serve leap-smeared time.


signature.asc
Description: PGP signature


Bug#974845: chrony: Add leapsecond info

2020-11-15 Thread Kurt Roeckx
Package: chrony
Version: 4.0-2
Severity: wishlist

Hi,

Could you please add the following line to the default chrony.conf
file:
leapsectz right/UTC

And add a Depends on tzdata, so that the timezone info is
available.


Kurt