diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2005-06-21 13:50:30 +0000 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2005-06-21 13:50:30 +0000 |
| commit | fb654466a64ad59f81a83979eeefe6fef017336d (patch) | |
| tree | 2a88e3d835595f1887b7d34fc78a12755597d4d2 /man2/getitimer.2 | |
| parent | f10e41020d252ba77d6eef88308542fd43e4db22 (diff) | |
| download | man-pages-fb654466a64ad59f81a83979eeefe6fef017336d.tar.gz | |
Minor changes
Diffstat (limited to 'man2/getitimer.2')
| -rw-r--r-- | man2/getitimer.2 | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/man2/getitimer.2 b/man2/getitimer.2 index 7fa6a37151..c28571668c 100644 --- a/man2/getitimer.2 +++ b/man2/getitimer.2 @@ -110,6 +110,7 @@ are significant in determining the duration of a timer. Timers will never expire before the requested time, but may expire some (short) time afterwards, which depends on the system timer resolution and on the system load. +(But see BUGS below.) Upon expiration, a signal will be generated and the timer reset. If the timer expires while the process is active (always true for .BR ITIMER_VIRT ) @@ -164,7 +165,7 @@ approximately 24.86 days. On certain systems (including x86), the Linux kernel has a bug which will produce premature timer expirations of up to one jiffy under some circumstances. -.\" As at June 2005, the above holds in 2.4.x and 2.6.c (e.g., 2.6.12.) +.\" As at June 2005, the above holds in 2.4.x and 2.6.x (e.g., 2.6.12.) POSIX.1 says that .B setitimer |