Lines Matching full:second

134 at which a leap second occurs or at which the leap second table expires;
135 the second is a signed integer specifying the correction, which is the
140 Each pair denotes one leap second, either positive or negative,
142 the last pair denotes the leap second table's expiration time.
143 Each leap second is at the end of a UTC calendar month.
144 The first leap second has a nonnegative occurrence time,
145 and is a positive leap second if and only if its correction is positive;
146 the correction for each leap second after the first differs
147 from the previous leap second by either 1 for a positive leap second,
148 or \-1 for a negative leap second.
149 If the leap second table is empty, the leap-second correction is zero
152 the leap-second correction is zero if the first pair's correction is 1 or \-1,
195 the above header and data are followed by a second header and data,
197 eight bytes are used for each transition time or leap second time.
198 (Leap second counts remain four bytes.)
199 After the second header and data comes a newline-enclosed string
225 Second, as in TZ="XXX3EDT4,0/0,J365/23", DST is in effect all year if it starts
230 the first leap second record can have a correction that is neither
232 Also, if two or more leap second transitions are present and the last
234 denotes the expiration of the leap second table instead of a leap second;
236 releases will likely add leap second entries after the expiration, and
251 only if its leap second table either expires or is truncated at the start.
270 When a TZif file contains a leap second table expiration
292 When a positive leap second occurs, readers should append an extra
293 second to the local minute containing the second just before the leap
294 second.
296 seconds, the leap second occurs earlier than the last second of the
365 conformance to RFC 8536, reject version 4 files whose leap second
447 a positive leap second 78796801 (1972-06-30 23:59:60 UTC), some readers will