From 805729e206b7586c57483aa0f4a90f7e0e2c9661 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 14 Oct 2015 22:54:08 +0000 Subject: - Remove /etc/leapsecs.dat - Publish tools to create the leap second table as a .c - Simplify functions using leap seconds - rc for 2.3.8.0 --- doc/libstddjb/tai.html | 25 +------------------------ 1 file changed, 1 insertion(+), 24 deletions(-) (limited to 'doc/libstddjb/tai.html') diff --git a/doc/libstddjb/tai.html b/doc/libstddjb/tai.html index a285cfb..231c0d1 100644 --- a/doc/libstddjb/tai.html +++ b/doc/libstddjb/tai.html @@ -112,28 +112,6 @@ dates. It is up to the programmer to make sure that a relative time is never interpreted as an absolute TAI64 date, and vice-versa.

-

The leap second table

- -

- skalibs provides a src/etc/leapsecs.dat file, -which is copied to /etc/leapsecs.dat at installation time -(or wherever you specified with the --prefix or --datadir -options to configure). -Make sure this file is always present and readable. -This file contains the leap second table, which is needed for -conversions between TAI and UTC. If you call a function that needs such -a conversion (for instance, you call tain_sysclock() and your -system clock is set to UTC) and the file cannot be read, the function -call will fail. -

- -

- The leap second table is read once in every process that needs it -(the first time a TAI ↔ UTC conversion is made) and then is -stored in memory. If the leapsecs.dat file changes, long-lived -processes will need to be restarted to take the change into account. -

-

Functions

Wallclock operations

@@ -343,8 +321,7 @@ could not be performed; in which case errno is set to EINVAL if the input argument was not a valid timestamp, to EOVERFLOW if the output could not be represented in the chosen format (which may happen on systems with a 32 bit time_t), or other error -codes - for instance related to the leap second table when a -lookup was necessary. +codes.

int tai_from_time_sysclock (tai_t *a, time_t t)
-- cgit v1.2.3