Home
last modified time | relevance | path

Searched refs:leap (Results 1 – 25 of 125) sorted by relevance

12345

/freebsd/contrib/ntp/scripts/update-leap/
H A DMakefile.am18 EXTRA_SCRIPTS= update-leap
23 man_MANS= update-leap.$(UPDATE_LEAP_MS)
25 noinst_MANS= update-leap.$(UPDATE_LEAP_MS)
29 invoke-update-leap.menu \
30 invoke-update-leap.texi \
31 update-leap-opts.def \
32 update-leap-opts \
33 update-leap.1update-leapman \
34 update-leap.1update-leapmdoc \
35 update-leap.in \
[all …]
H A Dupdate-leap.texi3 @setfilename update-leap.info
4 @settitle update-leap User's Manual
10 This file documents the use of @code{update-leap},
18 * update-leap: (update-leap). Check the leapfile and update it if needed.
22 @title update-leap User's Manual
23 @subtitle update-leap, version @value{VERSION}, @value{UPDATED}
30 @node Top, update-leap Description, (dir), (dir)
32 This document describes the use of the NTP Project's @code{update-leap} program.
34 This document applies to version @value{VERSION} of @code{update-leap}.
39 * update-leap Description:: Description
[all …]
H A Dinvoke-update-leap.texi1 @node update-leap Invocation
2 @section Invoking update-leap
3 @pindex update-leap
4 @cindex leap-seconds file manager/updater
7 # EDIT THIS FILE WITH CAUTION (invoke-update-leap.texi)
10 # From the definitions update-leap-opts.def
16 @code{update-leap}
18 and if necessary, updates leap-second definition file.
33 This can be run as a cron job. As the file is rarely updated, and leap
42 using the @code{agtexi-cmd} template and the option descriptions for the @code{update-leap} progra
[all...]
H A DMakefile.in92 subdir = scripts/update-leap
139 CONFIG_CLEAN_FILES = update-leap
198 am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/update-leap.in
484 EXTRA_SCRIPTS = update-leap
487 @INSTALL_UPDATE_LEAP_TRUE@man_MANS = update-leap.$(UPDATE_LEAP_MS)
488 @INSTALL_UPDATE_LEAP_FALSE@noinst_MANS = update-leap.$(UPDATE_LEAP_MS)
490 invoke-update-leap.menu \
491 invoke-update-leap.texi \
492 update-leap-opts.def \
493 update-leap
[all...]
H A Dupdate-leap-opts1 # EDIT THIS FILE WITH CAUTION (update-leap-opts)
4 # From the definitions update-leap-opts.def
49 update-leap - leap-seconds file manager/updater - Ver. 4.2.8p18
50 USAGE: update-leap [ -<flag> [<val>] | --<name>[{=| }<val>] ]...
H A Dinvoke-update-leap.menu1 * update-leap Invocation:: Invoking update-leap
/freebsd/contrib/ntp/
H A DREADME.leapsmear11 Unfortunately, leap seconds are scheduled to be inserted into or deleted
17 prescribed way to handle leap seconds in POSIX.
19 Whenever a leap second is to be handled ntpd either:
21 - passes the leap second announcement down to the OS kernel (if the OS
22 supports this) and the kernel handles the leap second automatically, or
24 - applies the leap second correction itself.
26 NTP servers also pass a leap second warning flag down to their clients via
28 approaching leap second, and can handle the leap second appropriately.
33 If a leap second is to be inserted then in most Unix-like systems the OS
34 kernel just steps the time back by 1 second at the beginning of the leap
[all …]
/freebsd/contrib/tzdata/
H A Dleapseconds1 # Allowance for leap seconds added to each time zone file.
6 # NIST/IERS format leap-seconds.list file, which can be copied from
7 # <https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list>
9 # <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>.
10 # For more about leap-seconds.list, please see
12 # <https://www.eecis.udel.edu/~mills/leap.html>.
14 # The rules for leap seconds are specified in Annex 1 (Time scales) of:
20 # periodically uses leap seconds to keep UTC to within 0.9 s of UT1
22 # and publishes leap second data in a copyrighted file
24 # See: Levine J. Coordinated Universal Time and the leap secon
[all...]
H A DMakefile142 # seconds since the epoch (not counting leap seconds), use
145 # as seconds since the epoch (counting leap seconds), use
147 # below. If you want both sets of data available, with leap seconds not
150 # below. If you want both sets of data available, with leap seconds counted
153 # below. POSIX mandates that leap seconds not be counted; for compatibility
155 # leap smearing; this can work better than unsmeared "right" time with
156 # applications that are not leap second aware, and is closer to unsmeared
173 # (optionally incorporating leap second information), use
175 # To install text data without leap second information (e.g., because
449 # Where to fetch leap
[all...]
H A Dleap-seconds.list20 # than 0.9 seconds. Therefore, when necessary a "leap second" is applied to UTC.
24 # theoretically possible to have a negative leap second (a second removed from UTC), but so far,
25 # all leap seconds have been positive (a second has been added to UTC). Based on what we know about
26 # the earth's rotation, it is unlikely that we will ever have a negative leap second.
30 # The first leap second was added on June 30, 1972. Until the year 2000, it was necessary in average to add a
31 # leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with an
36 # The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Center of
38 # Observatory. According to international agreements, leap seconds should be scheduled only for certain dates:
40 # and September. Since the introduction of leap second
[all...]
/freebsd/contrib/ntp/scripts/ntp-wait/
H A Dntp-wait.in36 if (!exists $info->{status_line}{leap}) {
41 my $leap = $info->{status_line}{leap};
44 if ($leap =~ /(sync|leap)_alarm/) {
50 if ($leap =~ /leap_(none|((add|del)_sec))/) {
56 print "\bUnexpected 'leap' status <$leap>\n";
/freebsd/contrib/ntp/ntpd/
H A Drefclock_local.c120 pp->leap = LEAP_NOTINSYNC; in local_start()
134 * system calls, the leap bits are extracted from the kernel. If there
135 * is a kernel error or the kernel leap bits are set to 11, the NTP leap
137 * NTP leap bits are set to the kernel leap bits and the stratum is set
181 * the leap bits and quality indicators from the kernel. in local_poll()
187 pp->leap = LEAP_NOWARNING; in local_poll()
192 pp->leap = LEAP_ADDSECOND; in local_poll()
197 pp->leap in local_poll()
[all...]
H A Drefclock_acts.c728 u_int leap; /* ACTS leap indicator */ in acts_timecode() local
735 char leapchar; /* WWVB leap indicator */ in acts_timecode()
739 int leapmonth; /* PTB/NPL month of leap */ in acts_timecode()
740 char leapdir; /* PTB/NPL leap direction */ in acts_timecode()
770 &pp->minute, &pp->second, &dst, &leap, &dut1, in acts_timecode()
776 pp->leap = LEAP_NOWARNING; in acts_timecode()
777 if (leap == 1) in acts_timecode()
778 pp->leap = LEAP_ADDSECOND; in acts_timecode()
779 else if (leap in acts_timecode()
[all...]
H A Drefclock_hopfpci.c74 #define LEWAPWAR 0x20 /* leap second warning bit */
88 char leap_status; /* leap second flag */
211 pp->leap = LEAP_ADDSECOND; in hopfpci_poll()
213 pp->leap = LEAP_NOWARNING; in hopfpci_poll()
229 pp->leap = LEAP_NOTINSYNC; in hopfpci_poll()
241 pp->leap = LEAP_NOTINSYNC; in hopfpci_poll()
H A Drefclock_tsyncpci.c518 /* Read the leap seconds info from the TSYNC-PCI device */ in tsync_poll()
555 // Extract leap second info from ioctl payload and perform byte swapping in tsync_poll()
651 // Subtract leap second info by one second to determine effective day in tsync_poll()
654 // If there is a leap second today and the KTS is using a time scale in tsync_poll()
655 // which handles leap seconds then in tsync_poll()
663 pp->leap = LEAP_ADDSECOND; in tsync_poll()
668 pp->leap = LEAP_DELSECOND; in tsync_poll()
670 // Else report no leap second pending (no handling of offsets in tsync_poll()
674 pp->leap = LEAP_NOWARNING; in tsync_poll()
677 // Else report no leap secon in tsync_poll()
[all...]
H A Drefclock_hopfser.c84 char leap_status; /* leap second flag */
257 (pp->second > 60) /*Allow for leap seconds.*/ || in hopfserial_receive()
269 pp->leap=0; in hopfserial_receive()
294 pp->leap = LEAP_NOTINSYNC; in hopfserial_receive()
303 pp->leap = LEAP_NOTINSYNC; in hopfserial_receive()
315 pp->leap = LEAP_NOTINSYNC; in hopfserial_receive()
H A Drefclock_ulink.c198 char leapchar; /* leap indicator */ in ulink_receive()
269 * + Leap year indicator. '+' if a leap year, in ulink_receive()
285 * to 'I' or 'D' during month preceding leap in ulink_receive()
341 * + Leap year indicator. '+' if a leap year, in ulink_receive()
357 * to '+' or '-' during month preceding leap in ulink_receive()
412 * + = '+' if current year is a leap year, else ' ' in ulink_receive()
508 * Decode synchronization, and leap characters. If in ulink_receive()
509 * unsynchronized, set the leap bits accordingly and exit. in ulink_receive()
510 * Otherwise, set the leap bits according to the leap characte in ulink_receive()
[all...]
H A Drefclock_shm.c101 int leap; member
372 int leap; member
505 shm_stat->leap = shmcopy.leap; in shm_query()
635 pp->leap = shm_stat.leap; in shm_timer()
H A Drefclock_hpgps.c108 * Viva la leap.
469 /* not a leap year */ in hpgps_receive()
477 /* a leap year */ in hpgps_receive()
532 pp->leap = LEAP_NOTINSYNC; in hpgps_receive()
535 pp->leap = LEAP_NOWARNING; in hpgps_receive()
542 * Ignore leap announcements unless June or December. in hpgps_receive()
548 pp->leap = LEAP_ADDSECOND; in hpgps_receive()
553 pp->leap = LEAP_DELSECOND; in hpgps_receive()
559 printf("hpgps: unrecognized leap indicator: %c\n", in hpgps_receive()
/freebsd/contrib/tzcode/
H A DMakefile142 # seconds since the epoch (not counting leap seconds), use
145 # as seconds since the epoch (counting leap seconds), use
147 # below. If you want both sets of data available, with leap seconds not
150 # below. If you want both sets of data available, with leap seconds counted
153 # below. POSIX mandates that leap seconds not be counted; for compatibility
155 # leap smearing; this can work better than unsmeared "right" time with
156 # applications that are not leap second aware, and is closer to unsmeared
173 # (optionally incorporating leap second information), use
175 # To install text data without leap second information (e.g., because
447 # Where to fetch leap
[all...]
/freebsd/usr.sbin/ntp/ntpd/
H A Dleap-seconds20 # than 0.9 seconds. Therefore, when necessary a "leap second" is applied to UTC.
24 # theoretically possible to have a negative leap second (a second removed from UTC), but so far,
25 # all leap seconds have been positive (a second has been added to UTC). Based on what we know about
26 # the earth's rotation, it is unlikely that we will ever have a negative leap second.
30 # The first leap second was added on June 30, 1972. Until the year 2000, it was necessary in averag…
31 # leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with…
36 # The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Cen…
38 # Observatory. According to international agreements, leap seconds should be scheduled only for cer…
40 # and September. Since the introduction of leap seconds in 1972, only dates in June and December we…
/freebsd/contrib/file/magic/Magdir/
H A Dtimezone18 >28 belong 0 \b, no leap seconds
19 >28 belong 1 \b, 1 leap second
20 >28 belong >1 \b, %d leap seconds
/freebsd/contrib/ntp/util/
H A Dtg.c243 int leap = 0; /* leap indicator */ variable
291 leap++; in main()
425 if (leap) { in main()
428 leap = 0; in main()
525 if (leap) { in main()
H A Dsht.c39 int leap; member
154 p->leap=atoi(argp+1); in main()
178 p->leap, p->precision, p->nsamples, p->valid); in main()
/freebsd/contrib/ntp/scripts/stats/
H A DREADME.stats227 UTC leap-second information
229 These data determine when the next leap second is to occur. The exact
236 +9.0000E+00 current leap seconds (s)
237 +2.0480E+05 time for leap seconds (s)
238 +2.0100E+02 week number for delta leap (weeks)
239 +1.9100E+02 week number for future leap (weeks)
240 +4.0000E+00 day number for future leap (days)
241 +9.0000E+00 future leap seconds (s)

12345