From e92e5cbc9c42a7f926eb4b25fdf6e52ec9d2fa4c Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Apr 2025 08:44:56 +0000 Subject: Update docs to latest posix version Signed-off-by: Laurent Bercot --- doc/libstddjb/tai.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/libstddjb/tai.html') diff --git a/doc/libstddjb/tai.html b/doc/libstddjb/tai.html index 080a9dd..65c90d8 100644 --- a/doc/libstddjb/tai.html +++ b/doc/libstddjb/tai.html @@ -64,7 +64,7 @@ on UTC, TAI and Unix time.

The meat and potatoes of all this is that programmers cannot simply rely on standard Unix APIs such as -gettimeofday() +gettimeofday() (which, by the way, is marked as obsolescent, but it's not going to disappear tomorrow) to measure time intervals or even to give precise absolute time, and in any case those APIs will become obsolete in 2038. @@ -96,10 +96,10 @@ precision. A tain structure holds an absolute date with a maximum of one-nanosecond precision, as permitted by the underlying system call. If flag-usert is clear, the system clock will be read via -gettimeofday() +gettimeofday() system call, which has a one-microsecond precision; if it is set, the system clock will be read via the -clock_gettime() +clock_gettime() system call, which has a one-nanosecond precision. In either case, a current tain will be unable to be more precise than the underlying implementation. @@ -180,7 +180,7 @@ start of a program.

The following two operations can only succeed if your system provides the -clock_gettime() +clock_gettime() primitive with at least one of the CLOCK_MONOTONIC or CLOCK_BOOTTIME clocks. Otherwise, they will fail with errno set to ENOSYS.

@@ -333,7 +333,7 @@ depending on whether skalibs was compiled with the --enable-tai-clock configure option). This is useful to get valid TAI/TAI64N timestamps out of information exported by the system, for instance the time_t -returned by time(), +returned by time(), or in the st_atim, st_mtim or st_ctim fields of a struct stat.

-- cgit v1.3.1