clock_getres.2: Update text on nonsetabble CLOCK_*_CPUTIME_ID clocks

SUSv3 permits, but does not require CLOCK_THREAD_CPUTIME_ID and
CLOCK_PROCESS_CPUTIME_ID to be settable.
See http://bugzilla.kernel.org/show_bug.cgi?id=11972.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2010-02-03 04:27:11 +01:00
parent 137d81b536
commit a113440ce6
1 changed files with 9 additions and 8 deletions

View File

@ -27,7 +27,7 @@
.\" 2003-08-24 aeb, large parts rewritten
.\" 2004-08-06 Christoph Lameter <clameter@sgi.com>, SMP note
.\"
.TH CLOCK_GETRES 2 2009-02-05 "" "Linux Programmer's Manual"
.TH CLOCK_GETRES 2 2010-02-03 "" "Linux Programmer's Manual"
.SH NAME
clock_getres, clock_gettime, clock_settime \- clock and time functions
.SH SYNOPSIS
@ -155,6 +155,9 @@ points outside the accessible address space.
The
.I clk_id
specified is not supported on this system.
.\" Linux also gives this error on attempts to set CLOCK_PROCESS_CPUTIME_ID
.\" and CLOCK_THREAD_CPUTIME_ID, when probably the proper error should be
.\" EPERM.
.TP
.B EPERM
.BR clock_settime ()
@ -209,17 +212,15 @@ Kernel).
Typically these offsets are small and therefore the effects may be
negligible in most cases.
.SH BUGS
According to POSIX.1-2001, the
According to POSIX.1-2001, a process with "appropriate privileges" may set the
.B CLOCK_PROCESS_CPUTIME_ID
and
.B CLOCK_THREAD_CPUTIME_ID
clocks should be settable using
clocks using
.BR clock_settime ().
However, the clocks currently
.\" Linux 2.6.28
are not settable.
.\" FIXME . Track the following bug report
.\" http://bugzilla.kernel.org/show_bug.cgi?id=11972
On Linux, these clocks are not settable
(i.e., no process has "appropriate privileges").
.\" See http://bugzilla.kernel.org/show_bug.cgi?id=11972
.SH "SEE ALSO"
.BR date (1),
.BR adjtimex (2),