Describe upper limit based on itimerfix restriction

This commit is contained in:
ache 1997-08-14 07:44:57 +00:00
parent 44b71ca022
commit 1bb5ca7c1e
2 changed files with 17 additions and 4 deletions

View File

@ -60,10 +60,14 @@ will supersede the prior call.
The request
.Fn alarm "0"
voids the current
alarm and the signal SIGALRM will not be delivered. The maximum number of
alarm and the signal SIGALRM will not be delivered.
.Pp
Due to
.Xr setitimer 2
restriction the maximum number of
.Ar seconds
allowed
is 2147483647.
allowed is 100000000.
.Sh RETURN VALUES
.Pp
The return value of
.Fn alarm

View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" From: @(#)ualarm.3 8.2 (Berkeley) 4/19/94
.\" $Id: ualarm.3,v 1.5 1997/02/22 14:58:19 peter Exp $
.\" $Id: ualarm.3,v 1.6 1997/08/14 06:32:25 ache Exp $
.\"
.Dd April 19, 1994
.Dt UALARM 3
@ -67,6 +67,15 @@ to the process every
microseconds after the timer expires (e.g. after
.Fa value
microseconds have passed).
.Pp
Due to
.Xr setitimer 2
restriction the maximum number of
.Ar microseconds
and
.Ar interval
is limited to 100000000000000
(in case this value fit in the unsigned integer).
.Sh RETURN VALUES
When the signal has successfully been caught,
.Fn ualarm