From a215069794f224d511a6863ca83b12b3fe868c0e Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sun, 29 Mar 2020 22:08:10 +0200 Subject: [PATCH] clock_getres.2: Move text in BUGS to NOTES The fact that CLOCK_PROCESS_CPUTIME_ID and CLOCK_PROCESS_CPUTIME_ID are not settable isn't a bug, since POSIX does allow the possibility that these clocks are not settable. Signed-off-by: Michael Kerrisk --- man2/clock_getres.2 | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/man2/clock_getres.2 b/man2/clock_getres.2 index c59f3d0ca..5395f9fbf 100644 --- a/man2/clock_getres.2 +++ b/man2/clock_getres.2 @@ -300,6 +300,16 @@ function; nor on the expiration of relative timers based upon this clock. Consequently, these time services shall expire when the requested relative interval elapses, independently of the new or old value of the clock. .RE +.PP +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 using +.BR clock_settime (). +On Linux, these clocks are not settable +(i.e., no process has "appropriate privileges"). +.\" See http://bugzilla.kernel.org/show_bug.cgi?id=11972 .\" .SS C library/kernel differences On some architectures, an implementation of @@ -348,16 +358,6 @@ and .BR CLOCK_THREAD_CPUTIME_ID , on systems that provide such an implementation (i.e., Linux 2.6.12 and later). -.SH BUGS -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 using -.BR clock_settime (). -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 gettimeofday (2),