diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2006-04-26 04:42:14 +0000 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2006-04-26 04:42:14 +0000 |
| commit | a8bbb90693f8cf2cd06ae20fd42a30aac9fbd7ff (patch) | |
| tree | 46402c3f170e6dded7bfa259b7e87d748913743f /man2/getitimer.2 | |
| parent | bb47b54bfbedda28691f5cd6ebdd90a1084449ad (diff) | |
| download | man-pages-a8bbb90693f8cf2cd06ae20fd42a30aac9fbd7ff.tar.gz | |
Updated discussion of maximum timer value to reflect the fact
that the default jiffy is now 4 milliseconds.
Added a FIXME.
Diffstat (limited to 'man2/getitimer.2')
| -rw-r--r-- | man2/getitimer.2 | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/man2/getitimer.2 b/man2/getitimer.2 index 43ab7decb3..68f2eeb487 100644 --- a/man2/getitimer.2 +++ b/man2/getitimer.2 @@ -149,9 +149,10 @@ 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 2.6 on x86 (where a jiffy is 0.001 seconds), +On Linux/x86 (where, since kerenl 2.6.13, +the default jiffy is 0.004 seconds), this means that the ceiling value for a timer is -approximately 24.86 days. +approximately 99.42 days. On certain systems (including x86), Linux kernels before version 2.6.12 have a bug which will produce @@ -167,3 +168,6 @@ 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. +.\" FIXME . Bugzilla report 25 Apr 2006: +.\" http://bugzilla.kernel.org/show_bug.cgi?id=6443 +.\" "setitimer() should reject non-canonical arguments" |