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.226
1 files changed, 13 insertions, 13 deletions
diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index edc1ff6ab..cf2f15d11 100644
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
@@ -18,7 +18,7 @@ Real-time library
.P
.RS -4
Feature Test Macro Requirements for glibc (see
-.BR feature_test_macros (7)):
+.MR feature_test_macros 7 ):
.RE
.P
.BR timer_getoverrun ():
@@ -51,7 +51,7 @@ or because the signal may be temporarily blocked,
there can be a delay between the time when the notification
signal is generated and the time when it
is delivered (e.g., caught by a signal handler) or accepted (e.g., using
-.BR sigwaitinfo (2)).
+.MR sigwaitinfo 2 ).
In this interval, further timer expirations may occur.
The timer overrun count is the number of additional
timer expirations that occurred between the time when the signal
@@ -83,7 +83,7 @@ on Linux it is also possible to obtain the overrun count via the
field of the
.I siginfo_t
structure (see
-.BR sigaction (2)).
+.MR 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.
@@ -121,14 +121,14 @@ in
in this case (and the overrun value is reset to 0).
.SH EXAMPLES
See
-.BR timer_create (2).
+.MR timer_create 2 .
.SH SEE ALSO
-.BR clock_gettime (2),
-.BR sigaction (2),
-.BR signalfd (2),
-.BR sigwaitinfo (2),
-.BR timer_create (2),
-.BR timer_delete (2),
-.BR timer_settime (2),
-.BR signal (7),
-.BR time (7)
+.MR clock_gettime 2 ,
+.MR sigaction 2 ,
+.MR signalfd 2 ,
+.MR sigwaitinfo 2 ,
+.MR timer_create 2 ,
+.MR timer_delete 2 ,
+.MR timer_settime 2 ,
+.MR signal 7 ,
+.MR time 7