Re: [PATCH] getrlimit.2: Mention unit used by RLIMIT_CORE and RLIMIT_FSIZE
From: Michael Kerrisk (man-pages) <hidden>
Date: 2017-09-03 00:49:12
Hello Thiago, On 09/01/2017 10:27 PM, Thiago Jung Bauermann wrote:
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.
Thanks. That was a silly deficiency on the man page. Patch applied. I also fixed a similar problem with RLIMIT_DATA. Cheers, Michael
quoted hunk
Signed-off-by: Thiago Jung Bauermann <redacted> --- man2/getrlimit.2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)diff --git a/man2/getrlimit.2 b/man2/getrlimit.2 index 84f04d695ea2..f2c5297526d7 100644 --- a/man2/getrlimit.2 +++ b/man2/getrlimit.2@@ -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.
-- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html