s...@eskimo.com said:
> There's a path via which NTP or some other external program can set it, but I
> haven't seen an NTP server in the wild that knows how and is configured to do
> so. (I'd love to be proved wrong on this, though.)
ntpd has an option to read a leap file. That sets the TAI
Systems that need a leap second free time scale these days seem to be using GPS
time instead of TAI. It seems to be rather popular in the financial industry.
___
time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe, go to
On 8/8/19 4:24 AM, Greg Troxel wrote:
The POSIX specification says that unix time (what gettimeofday returns,
the numbers that are stored in the filesystem for mod times) is a
strange version of UTC, where it's expressed in seconds since the epoch
as if there were no leap seconds.
which is
On 8/8/19 2:51 AM, Tim Dunker wrote:
Dear Ralph
I keep all our GNU/Linux machines on UTC (i.e., <>). Our
timezone is off by one or two hours, but the actual offset does not
matter to me. What matters to me is to have all systems using the same
timezone, and for our purposes, nobody cares about
Ralph Aichinger wrote:
> TAI would probably be the more logical way to store and do
> calculations with time, only including leap seconds when
> formatting time for human consumption.
Indeed. Just about everybody I know who's studied this issue
carefully has come to more or less the same
On 8/8/19 1:30 AM, Ralph Aichinger wrote:
Hi!
Another newbie type question: When thinking about how computers represent
time,
TAI would probably be the more logical way to store and do calculations
with time, only including leap seconds when formatting time for human
consumption. Or am I wrong
Ralph Aichinger writes:
> Another newbie type question: When thinking about how computers
> represent time, TAI would probably be the more logical way to store
> and do calculations with time, only including leap seconds when
> formatting time for human consumption. Or am I wrong in this?
There
Dear Ralph
I keep all our GNU/Linux machines on UTC (i.e., <>). Our
timezone is off by one or two hours, but the actual offset does not
matter to me. What matters to me is to have all systems using the same
timezone, and for our purposes, nobody cares about our local time.
>> Can the same thing
Hi!
Another newbie type question: When thinking about how computers represent
time,
TAI would probably be the more logical way to store and do calculations
with time, only including leap seconds when formatting time for human
consumption. Or am I wrong
in this?
There is a CLOCK_TAI on Linux, but
