Re: sntpclock = ntpdate + 22s
[email protected] (Paul Jarc) Wed, 06 Jun 2007 16:46:48 -0400
| Newsgroups | gmane.comp.lib.libtai |
|---|---|
| Organization | What did you have in mind? A short, blunt, human pyramid? |
| Message-ID | <[email protected]> |
johnea <[email protected]> wrote: > 22 seconds. That's the current difference (almost - it's actually 23 now) between a system clock keeping TAI time (a count of seconds since the beginning of 1970) and a clock keeping POSIX time (a count of only non-leap seconds since the beginning of 1970). A TAI clock increases smoothly; a POSIX clock jumps back a second when a leap second occurs. POSIX is more common overall, but clockspeed users tend to use TAI. Doubts about whether your clock is synchronized usually stem from a misconfiguration, where you clock is interpreted as TAI by some programs and as POSIX by other. To use a TAI clock, you should have the /etc/leapsecs.dat file installed by clockspeed, and you should use a right/ time zone (e.g., right/America/Los_Angeles instead of America/Los_Angeles). To use a POSIX clock, you should delete /etc/leapsecs.dat and use a non-right/ time zone. If you use a POSIX clock, then when a leap second occurs, you'll have to restart clockspeed, and either use clockadd to make the one-second jump while clockspeed isn't running, or let clockspeed bring your clock back into sync slowly. paul