From d8c2f63fc329cc3d7dfc17bc54002855ad7cb22c Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sat, 18 Apr 2015 08:34:06 +0200 Subject: [PATCH] timer_getoverrun.2: CONFORMING TO: add POSIX.1-2008 Signed-off-by: Michael Kerrisk --- man2/timer_getoverrun.2 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2 index c14230bb2..f50190461 100644 --- a/man2/timer_getoverrun.2 +++ b/man2/timer_getoverrun.2 @@ -59,7 +59,7 @@ overruns can occur as follows. Regardless of whether or not a real-time signal is used for timer notifications, the system queues at most one signal per timer. -(This is the behavior specified by POSIX.1-2001. +(This is the behavior specified by POSIX.1. The alternative, queuing one signal for each timer expiration, could easily result in overflowing the allowed limits for queued signals on the system.) @@ -95,7 +95,7 @@ is not a valid timer ID. .SH VERSIONS This system call is available since Linux 2.6. .SH CONFORMING TO -POSIX.1-2001. +POSIX.1-2001, POSIX.1-2008. .SH NOTES When timer notifications are delivered via signals .RB ( SIGEV_SIGNAL ), @@ -107,13 +107,13 @@ structure (see .BR sigaction (2)). This allows an application to avoid the overhead of making a system call to obtain the overrun count, -but is a nonportable extension to POSIX.1-2001. +but is a nonportable extension to POSIX.1. -POSIX.1-2001 discusses timer overruns only in the context of +POSIX.1 discusses timer overruns only in the context of timer notifications using signals. .\" FIXME . Austin bug filed, 11 Feb 09 .SH BUGS -POSIX.1-2001 specifies that if the timer overrun count +POSIX.1 specifies that if the timer overrun count is equal to or greater than an implementation-defined maximum, .BR DELAYTIMER_MAX , then