cpu -> CPU, from jmc@openbsd.
This commit is contained in:
parent
3013c9b400
commit
22c09256dd
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: getrlimit.2,v 1.24 2003/04/16 13:34:52 wiz Exp $
|
||||
.\" $NetBSD: getrlimit.2,v 1.25 2003/07/14 08:58:57 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1991, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -68,7 +68,7 @@ The largest size (in bytes)
|
|||
.Pa core
|
||||
file that may be created.
|
||||
.It Li RLIMIT_CPU
|
||||
The maximum amount of cpu time (in seconds) to be used by
|
||||
The maximum amount of CPU time (in seconds) to be used by
|
||||
each process.
|
||||
.It Li RLIMIT_DATA
|
||||
The maximum size (in bytes) of the data segment for a process;
|
||||
|
@ -100,7 +100,7 @@ Stack extension is performed automatically by the system.
|
|||
.Pp
|
||||
A resource limit is specified as a soft limit and a hard limit.
|
||||
When a soft limit is exceeded a process may receive a signal (for example,
|
||||
if the cpu time or file size is exceeded), but it will be allowed to
|
||||
if the CPU time or file size is exceeded), but it will be allowed to
|
||||
continue execution until it reaches the hard limit (or modifies
|
||||
its resource limit).
|
||||
The
|
||||
|
@ -154,7 +154,7 @@ soft limit will cause the write to fail and a signal
|
|||
.Dv SIGXFSZ
|
||||
to be
|
||||
generated; this normally terminates the process, but may be caught.
|
||||
When the soft cpu time limit is exceeded, a signal
|
||||
When the soft CPU time limit is exceeded, a signal
|
||||
.Dv SIGXCPU
|
||||
is sent to the
|
||||
offending process.
|
||||
|
|
Loading…
Reference in New Issue