mirror of git://sourceware.org/git/glibc.git
manual: make setrlimit() description less ambiguous
The existing description for setrlimit() has some ambiguity. It could be
understood to have the semantics of getrlimit(), i.e., the limits from the
process are stored in the provided rlp pointer.
Make the description more explicit that rlp are the input values, and that
the limits of the process is changed with this function.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
(cherry picked from commit aedbf08891
)
This commit is contained in:
parent
b71a51189d
commit
4bdcc1963b
|
@ -192,8 +192,8 @@ If the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
|
|||
@standards{BSD, sys/resource.h}
|
||||
@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
|
||||
@c Direct syscall on most systems; lock-taking critical section on HURD.
|
||||
Store the current and maximum limits for the resource @var{resource}
|
||||
in @code{*@var{rlp}}.
|
||||
Change the current and maximum limits of the process for the resource
|
||||
@var{resource} to the values provided in @code{*@var{rlp}}.
|
||||
|
||||
The return value is @code{0} on success and @code{-1} on failure. The
|
||||
following @code{errno} error condition is possible:
|
||||
|
|
Loading…
Reference in New Issue