Lines Matching refs:leap

71 #	4. The decision to insert a leap second into UTC is currently
86 #	of dropping seconds ("negative" leap seconds), this has
93 #	leap second is not well defined. The official name of that leap
97 #	one second during the leap second and use a time that is equivalent
101 #	is used for the second time. Thus the leap second which
111 #	If your system realizes the leap second by repeating 00:00:00 UTC twice
128 #	This complexity would not be needed for negative leap seconds (if they
133 #	during the leap second does not arise.
135 #	Some systems implement leap seconds by amortizing the leap second
138 #	negative) leap second. This method removes the time step described
151 #	Last Update of leap second values:   8 July 2016
155 #	the leap second data was added to the file. This line can
176 #	The data in this file will be updated periodically as new leap
179 #	file name leap-seconds to form the name leap-seconds.<NTP TIME>.
180 #	In addition, the generic name leap-seconds.list will always point to
183 #	This update procedure will be performed only when a new leap second
189 #	at least twice per year whether or not a new leap second is
194 #	leap seconds.) This expiration date will be identified by a
196 #	In the unlikely event that a leap second is announced with an
198 #	file will be edited to include that leap second as soon as it is
201 #	If an announcement by the IERS specifies that no leap second is