aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2009-02-08 10:10:39 +1300
committerMichael Kerrisk <mtk.manpages@gmail.com>2009-02-09 12:32:00 +1300
commit0eb443910b2bc6241e8e02995f5783faec891470 (patch)
treeed6630900ce162abbeace24bf0a123be41ecf89f
parentac48bb8a2927a824681311382fe7b3a6bb8e65b5 (diff)
downloadman-pages-0eb443910b2bc6241e8e02995f5783faec891470.tar.gz
clock_nanosleep.2, getrusage.2, timerfd_create.2, clock.3, clock_getcpuclockid.3, ftime.3, pthread_create.3, pthread_getcpuclockid.3, pthread_tryjoin_np.3, sem_wait.3, time.7: Global fix: Fix xrefs to clock_*.? pages to reflect move to section 2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat
-rw-r--r--man2/clock_nanosleep.210
-rw-r--r--man2/getrusage.24
-rw-r--r--man2/timerfd_create.22
-rw-r--r--man3/clock.34
-rw-r--r--man3/clock_getcpuclockid.36
-rw-r--r--man3/ftime.32
-rw-r--r--man3/pthread_create.32
-rw-r--r--man3/pthread_getcpuclockid.312
-rw-r--r--man3/pthread_tryjoin_np.32
-rw-r--r--man3/sem_wait.32
-rw-r--r--man7/time.74
11 files changed, 25 insertions, 25 deletions
diff --git a/man2/clock_nanosleep.2 b/man2/clock_nanosleep.2
index 075d65885b..44c6fa4368 100644
--- a/man2/clock_nanosleep.2
+++ b/man2/clock_nanosleep.2
@@ -88,7 +88,7 @@ by all threads in the process.
.\" to deal with the CLOCK_PROCESS_CPUTIME_ID case.
.PP
See
-.BR clock_getres (3)
+.BR clock_getres (2)
for further details on these clocks.
If
@@ -191,7 +191,7 @@ timer drift problems of the type described in
(Such problems are exacerbated in programs that try to restart
a relative sleep that is repeatedly interrupted by signals.)
To perform a relative sleep that avoids these problems, call
-.BR clock_gettime (3)
+.BR clock_gettime (2)
for the desired clock,
add the desired interval to the returned time value,
and then call
@@ -224,7 +224,7 @@ has no effect on signals dispositions or the signal mask.
POSIX.1 specifies that after changing the value of the
.B CLOCK_REALTIME
clock via
-.BR clock_settime (3),
+.BR clock_settime (2),
the new clock value shall be used to determine the time
at which a thread blocked on an absolute
.BR clock_nanosleep ()
@@ -237,13 +237,13 @@ POSIX.1 specifies that
changing the value of the
.B CLOCK_REALTIME
clock via
-.BR clock_settime (3)
+.BR clock_settime (2)
shall have no effect on a thread that is blocked on a relative
.BR clock_nanosleep ().
.SH "SEE ALSO"
.BR nanosleep (2),
.BR timer_create (2),
-.BR clock_getres (3),
+.BR clock_getres (2),
.BR sleep (3),
.BR usleep (3),
.BR time (7)
diff --git a/man2/getrusage.2 b/man2/getrusage.2
index 92a48d6f6d..5e9d83a724 100644
--- a/man2/getrusage.2
+++ b/man2/getrusage.2
@@ -159,9 +159,9 @@ See also the description of
in
.BR proc (5).
.SH "SEE ALSO"
+.BR clock_gettime (2),
.BR getrlimit (2),
.BR times (2),
.BR wait (2),
.BR wait4 (2),
-.BR clock (3),
-.BR clock_gettime (3)
+.BR clock (3)
diff --git a/man2/timerfd_create.2 b/man2/timerfd_create.2
index 403d3f9599..5f5928a96d 100644
--- a/man2/timerfd_create.2
+++ b/man2/timerfd_create.2
@@ -73,7 +73,7 @@ is a non-settable clock that is not affected
by discontinuous changes in the system clock
(e.g., manual changes to system time).
The current value of each of these clocks can be retrieved using
-.BR clock_gettime (3).
+.BR clock_gettime (2).
Starting with Linux 2.6.27, the following values may be bitwise ORed in
.IR flags
diff --git a/man3/clock.3 b/man3/clock.3
index 6729d4111a..704818f484 100644
--- a/man3/clock.3
+++ b/man3/clock.3
@@ -82,6 +82,6 @@ The
function, which explicitly returns (separate) information about the
caller and its children, may be preferable.
.SH "SEE ALSO"
+.BR clock_gettime (2),
.BR getrusage (2),
-.BR times (2),
-.BR clock_gettime (3)
+.BR times (2)
diff --git a/man3/clock_getcpuclockid.3 b/man3/clock_getcpuclockid.3
index ffca7134be..91869036f4 100644
--- a/man3/clock_getcpuclockid.3
+++ b/man3/clock_getcpuclockid.3
@@ -83,7 +83,7 @@ function is available in glibc since version 2.2.
POSIX.1-2001.
.SH NOTES
Calling
-.BR clock_gettime (3)
+.BR clock_gettime (2)
with the clock ID obtained by a call to
.BR clock_getcpuclockid ()
with a
@@ -95,7 +95,7 @@ is the same as using the clock ID
The example program below obtains the
CPU-time clock ID of the process whose ID is given on the command line,
and then uses
-.BR clock_gettime (3)
+.BR clock_gettime (2)
to obtain the time on that clock.
An example run is the following:
.in +4n
@@ -141,6 +141,6 @@ main(int argc, char *argv[])
}
.fi
.SH SEE ALSO
-.BR clock_getres (3),
+.BR clock_getres (2),
.BR pthread_getcpuclockid (3),
.BR time (7)
diff --git a/man3/ftime.3 b/man3/ftime.3
index a799382374..7e31e2734d 100644
--- a/man3/ftime.3
+++ b/man3/ftime.3
@@ -81,7 +81,7 @@ suffices,
can be used;
.BR gettimeofday (2)
gives microseconds;
-.BR clock_gettime (3)
+.BR clock_gettime (2)
gives nanoseconds but is not yet widely available.
.LP
Under libc4 and libc5 the \fImillitm\fP field is meaningful.
diff --git a/man3/pthread_create.3 b/man3/pthread_create.3
index b1ce3c2bd8..b587a1f187 100644
--- a/man3/pthread_create.3
+++ b/man3/pthread_create.3
@@ -103,7 +103,7 @@ The new thread inherits the calling thread's floating-point environment
The initial value of the new thread's CPU-time clock is 0
(see
.BR pthread_getcpuclockid (3)).
-.\" CLOCK_THREAD_CPUTIME_ID in clock_gettime(3)
+.\" CLOCK_THREAD_CPUTIME_ID in clock_gettime(2)
.SS Linux-specific details
The new thread inherits copies of the calling thread's capability sets
(see
diff --git a/man3/pthread_getcpuclockid.3 b/man3/pthread_getcpuclockid.3
index 791302de0f..23b40d989a 100644
--- a/man3/pthread_getcpuclockid.3
+++ b/man3/pthread_getcpuclockid.3
@@ -67,14 +67,14 @@ When
refers to the calling thread,
this function returns an identifier that refers to the same clock
manipulated by
-.BR clock_gettime (3)
+.BR clock_gettime (2)
and
-.BR clock_settime (3)
+.BR clock_settime (2)
when given the clock ID
.BR CLOCK_THREAD_CPUTIME_ID .
.SH EXAMPLE
The program below creates a thread and then uses
-.BR clock_gettime (3)
+.BR clock_gettime (2)
to retrieve the total process CPU time,
and the per-thread CPU time consumed by the two threads.
The following shell session shows an example run:
@@ -164,10 +164,10 @@ main(int argc, char *argv[])
}
.fi
.SH SEE ALSO
-.BR clock_gettime (3),
-.BR clock_settime (3),
-.BR clock_getcpuclockid (3),
+.BR clock_gettime (2),
+.BR clock_settime (2),
.BR timer_create (2),
+.BR clock_getcpuclockid (3),
.BR pthread_self (3),
.BR pthreads (7),
.BR time (7)
diff --git a/man3/pthread_tryjoin_np.3 b/man3/pthread_tryjoin_np.3
index 85a6f34605..0d5e5b5894 100644
--- a/man3/pthread_tryjoin_np.3
+++ b/man3/pthread_tryjoin_np.3
@@ -131,7 +131,7 @@ The following code waits to join for up to 5 seconds:
}
.fi
.SH SEE ALSO
-.BR clock_gettime (3),
+.BR clock_gettime (2),
.BR pthread_join (3),
.BR pthread_exit (3),
.BR pthreads (7)
diff --git a/man3/sem_wait.3 b/man3/sem_wait.3
index 1c848fd572..c799100919 100644
--- a/man3/sem_wait.3
+++ b/man3/sem_wait.3
@@ -262,7 +262,7 @@ main(int argc, char *argv[])
.fi
.SH "SEE ALSO"
.\" FIXME . when this page has been added to the man-pages set:
-.\" .BR clock_gettime (3),
+.\" .BR clock_gettime (2),
.BR sem_getvalue (3),
.BR sem_post (3),
.BR sem_overview (7),
diff --git a/man7/time.7 b/man7/time.7
index 1ef5cf418c..c38b9f8006 100644
--- a/man7/time.7
+++ b/man7/time.7
@@ -115,7 +115,7 @@ but instead can be as accurate as the hardware allows
(microsecond accuracy is typical of modern hardware).
You can determine whether high-resolution timers are supported by
checking the resolution returned by a call to
-.BR clock_getres (3)
+.BR clock_getres (2)
or looking at the "resolution" entries in
.IR /proc/timer_list .
@@ -177,6 +177,7 @@ and
.BR time (1),
.BR adjtimex (2),
.BR alarm (2),
+.BR clock_gettime (2),
.BR clock_nanosleep (2),
.BR getitimer (2),
.BR getrlimit (2),
@@ -192,7 +193,6 @@ and
.BR adjtime (3),
.BR clock (3),
.BR clock_getcpuclockid (3),
-.BR clock_gettime (3),
.BR ctime (3),
.BR pthread_getcpuclockid (3),
.BR sleep (3),
generated by cgit 1.2.3-korg (git 2.43.0) at 2025-11-30 10:23:49 +0000