mirror of https://github.com/mkerrisk/man-pages
getrlimit.2: Mention unit used by RLIMIT_CORE and RLIMIT_FSIZE
It would have been obvious that these limits are in bytes, except that "ulimit -a" in at least bash, dash and zsh says that they're in blocks. This confused me, so I had to check the kernel source code. My understanding is that they are indeed in bytes, so mention this information in the man page. Signed-off-by: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
df81149955
commit
4a63f626b5
|
@ -150,7 +150,7 @@ This is the maximum size of a
|
|||
.I core
|
||||
file (see
|
||||
.BR core (5))
|
||||
that the process may dump.
|
||||
in bytes that the process may dump.
|
||||
When 0 no core dump files are created.
|
||||
When nonzero, larger dumps are truncated to this size.
|
||||
.TP
|
||||
|
@ -187,7 +187,7 @@ which fail with the error
|
|||
upon encountering the soft limit of this resource.
|
||||
.TP
|
||||
.B RLIMIT_FSIZE
|
||||
This is the maximum size of files that the process may create.
|
||||
This is the maximum size in bytes of files that the process may create.
|
||||
Attempts to extend a file beyond this limit result in delivery of a
|
||||
.B SIGXFSZ
|
||||
signal.
|
||||
|
|
Loading…
Reference in New Issue