Re: [Ntp] Antw: Re: Finding leap-seconds.list

[Hal Murray <[e-mail]>]

[e-mail] said:
>> new TZ data should be made availale whenever a
>> new leapsecond file is available (or at least significantly
>> before the last one expires).

> Of course, but how long is "significantly"?

> In contrast, we reliably get about six months' notice for a leap second. We
> batch that into the next tzdb release, whenever it happens to occur for other
>  reasons. We've never had the problem of no timezone changes for six months
> so  this has been good enough for us. (We would make a release for leap
> seconds  reasons only, if need be.) 

I think things will be fine as long as you are willing to push out a leap-only 
release if nothing else happens for a month.  The point is that you don't get 
the whole 6 months.

Here is my list of the steps that have to happen for sites that get it via 
their distro:
  1: IERS announces leap or non-leap via bulletin C
  2: NIST updates leap-seconds.txt
  3 TZDB releases updated copy from NIST
  4  distro releases update to TZDB
  5  end system picks up new TZDB from distro
  6  ntpd announces to downstream clients
  
If we assume the first two steps take a month and allow a month each for steps 
3, 4, and 5, that still leaves a month of slop if the announcements are to get 
out a month early.


-- 
These are my opinions.  I hate spam.