mirror of https://github.com/mkerrisk/man-pages
clock_getres.3: CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID not settable
According to POSIX.1-2001, the CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID clocks should be settable, but currently they are not. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
4888dfbf49
commit
3847be7851
|
@ -27,7 +27,7 @@
|
|||
.\" 2003-08-24 aeb, large parts rewritten
|
||||
.\" 2004-08-06 Christoph Lameter <clameter@sgi.com>, SMP note
|
||||
.\"
|
||||
.TH CLOCK_GETRES 3 2008-08-11 "" "Linux Programmer's Manual"
|
||||
.TH CLOCK_GETRES 3 2008-11-07 "" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
clock_getres, clock_gettime, clock_settime \- clock and time functions
|
||||
.SH SYNOPSIS
|
||||
|
@ -201,6 +201,16 @@ Glibc contains no provisions to deal with these offsets (unlike the Linux
|
|||
Kernel).
|
||||
Typically these offsets are small and therefore the effects may be
|
||||
negligible in most cases.
|
||||
.SH BUGS
|
||||
According to POSIX.1-2001, the
|
||||
.B CLOCK_PROCESS_CPUTIME_ID
|
||||
and
|
||||
.B CLOCK_THREAD_CPUTIME_ID
|
||||
clocks should be settable using
|
||||
.BR clock_settime ().
|
||||
However, the clocks currently
|
||||
.\" Linux 2.6.28
|
||||
are not settable.
|
||||
.SH "SEE ALSO"
|
||||
.BR date (1),
|
||||
.BR adjtimex (2),
|
||||
|
|
Loading…
Reference in New Issue