[ntpwg] Further to the timestamping issue
Rob Seaman
seaman at noao.edu
Thu Jun 19 17:28:42 UTC 2008
TSG wrote:
> Do you have any idea of the cost of implementing a log management
> practice that will address multiple Leap Second's being added???
No, and neither do you.
You are also jousting with a windmill. Nothing would stop Gambis from
announcing a leap second for December 2011 at the same time as a leap
second for June 2009. (Dates chosen randomly.) Each would be handled
in sequence whether or not NTP is aware of both at the same time.
This is precisely a feature of UTC that has been requested. The
question is how best would NTP implement it.
> Considering also that Leap Second's are never added such that there
> would be more than one per month added,
Nice argument against leap hours :-)
> the accidental adding of a leap second (assuming NTP automatically
> tracks them) could cause billions or trillions of dollars of damage
Somebody who places auditing above all other requirements might want
to actually characterize the cost/schedule/performance benefits and
risks of the various alternatives :-)
Rob
More information about the ntpwg
mailing list