summaryrefslogtreecommitdiffstats
path: root/man2/timer_getoverrun.2
diff options
context:
space:
mode:
Diffstat (limited to 'man2/timer_getoverrun.2')
-rw-r--r--man2/timer_getoverrun.211
1 files changed, 6 insertions, 5 deletions
diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index e2a40d0b4..75219572e 100644
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
@@ -3,7 +3,7 @@
.\"
.\" SPDX-License-Identifier: Linux-man-pages-copyleft
.\"
-.TH timer_getoverrun 2 2022-10-30 "Linux man-pages 6.03"
+.TH timer_getoverrun 2 2023-03-30 "Linux man-pages 6.05.01"
.SH NAME
timer_getoverrun \- get overrun count for a POSIX per-process timer
.SH LIBRARY
@@ -76,10 +76,6 @@ is set to indicate the error.
.I timerid
is not a valid timer ID.
.SH VERSIONS
-This system call is available since Linux 2.6.
-.SH STANDARDS
-POSIX.1-2001, POSIX.1-2008.
-.SH NOTES
When timer notifications are delivered via signals
.RB ( SIGEV_SIGNAL ),
on Linux it is also possible to obtain the overrun count via the
@@ -96,6 +92,11 @@ POSIX.1 discusses timer overruns only in the context of
timer notifications using signals.
.\" FIXME . Austin bug filed, 11 Feb 09
.\" https://www.austingroupbugs.net/view.php?id=95
+.SH STANDARDS
+POSIX.1-2008.
+.SH HISTORY
+Linux 2.6.
+POSIX.1-2001.
.SH BUGS
POSIX.1 specifies that if the timer overrun count
is equal to or greater than an implementation-defined maximum,