LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

Added text to note that current incorrect behaviour of 

normalising tv_usec >= 1000000 will be repaired in a future
kernel; applications should be fixed now.
This commit is contained in:
Michael Kerrisk 2006-04-26 19:39:33 +00:00
parent eafd5ce11f
commit 563711249d
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
man2/getitimer.2
View File

@ -4,7 +4,7 @@
.\" Modified Tue Oct 22 00:22:35 EDT 1996 by Eric S. Raymond <esr@thyrsus.com>
.\" 2005-04-06 mtk, Matthias Lang <matthias@corelatus.se>
.\" Noted MAX_SEC_IN_JIFFIES ceiling
.TH GETITIMER 2 1993-08-05 "Linux 0.99.11" "Linux Programmer's Manual"
.TH GETITIMER 2 2006-04-27 "Linux 2.6.16" "Linux Programmer's Manual"
.SH NAME
getitimer, setitimer \- get or set value of an interval timer
.SH SYNOPSIS
@ -150,7 +150,7 @@ representation exceeds MAX_SEC_IN_JIFFIES
(defined in
.IR include/linux/jiffies.h ),
then the timer is silently truncated to this ceiling value.
On Linux/x86 (where, since kerenl 2.6.13,
On Linux/x86 (where, since kernel 2.6.13,
the default jiffy is 0.004 seconds),
this means that the ceiling value for a timer is
approximately 99.42 days.
@ -169,6 +169,15 @@ should fail if a
value is specified that is outside of the range 0 to 999999.
However, Linux does not give an error, but instead silently
adjusts the corresponding seconds value for the timer.
In the future, this non-conformance will be repaired:
existing applications should be fixed now to ensure that they supply
a properly formed
.I tv_usec
value.
.\" FIXME . Bugzilla report 25 Apr 2006:
.\" http://bugzilla.kernel.org/show_bug.cgi?id=6443
.\" "setitimer() should reject non-canonical arguments"
.\" The feedback on this report points to a kernel patch
.\" which apparently should result in this problem
.\" being fixed after a clean-up period of one year
.\" (i.e., March 2007).