[pkg-ntp-maintainers] [pkg-ntp] 09/13: Use tzdata leapfile in default configuration

[Bernhard Schmidt]

On 07.05.2017 22:21, Kurt Roeckx wrote:
> On Sun, May 07, 2017 at 07:44:07PM +0000, Bernhard Schmidt wrote:
>> diff --git a/debian/control b/debian/control
>> index 05e5b85..1762f55 100644
>> --- a/debian/control
>> +++ b/debian/control
>> @@ -12,7 +12,7 @@ Vcs-Git: https://anonscm.debian.org/git/pkg-ntp/pkg-ntp.git/
>>  
>>  Package: ntp
>>  Architecture: any
>> -Depends: adduser, lsb-base (>= 3.2-13), netbase, ${misc:Depends}, ${shlibs:Depends}
>> +Depends: adduser, lsb-base (>= 3.2-13), netbase, tzdata, ${misc:Depends}, ${shlibs:Depends}
>>  Pre-Depends: dpkg (>= 1.15.7.2)
>>  Recommends: ${perl:Depends}
>>  Suggests: ntp-doc
>> diff --git a/debian/ntp.conf b/debian/ntp.conf
>> index b51b4f9..d473b43 100644
>> --- a/debian/ntp.conf
>> +++ b/debian/ntp.conf
>> @@ -2,6 +2,9 @@
>>  
>>  driftfile /var/lib/ntp/ntp.drift
>>  
>> +# Leap seconds definition provided by tzdata
>> +leapfile /usr/share/zoneinfo/leap-seconds.list
>> +
>>  # Enable this if you want statistics to be logged.
>>  #statsdir /var/log/ntpstats/
> 
> This has been something I wanted to do for a long time, but I
> think we need a trigger on an update of that file to restart
> ntpd.

True that, we could file a wishlist bug for this on tzdata for Buster or
implement some monitoring on our own. I was somehow hoping that systemd
would support something like that (inotify on a file and restart the
service on change), but restart does not seem to be supported.

Fortunately looking at past tzdata versions the leap seconds are known
several months in advance and systems tracking stable-security probably
boot due to kernel updates more often than that. But a clean restart
would be nicer.

Bernhard