From: Thiago Jung Bauermann <bauerman-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] getrlimit.2: Mention unit used by RLIMIT_CORE and RLIMIT_FSIZE
Date: Sat, 02 Sep 2017 23:24:54 -0300 [thread overview]
Message-ID: <87fuc4semh.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <07aa1031-91b5-f1ca-b23f-858c06c3a9f8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Michael Kerrisk (man-pages) <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> 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.
Thanks!
> I also fixed a similar problem with RLIMIT_DATA.
I didn't occur to me to check the other resources. Thanks for doing that.
--
Thiago Jung Bauermann
IBM Linux Technology Center
--
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
next prev parent reply other threads:[~2017-09-03 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 20:27 [PATCH] getrlimit.2: Mention unit used by RLIMIT_CORE and RLIMIT_FSIZE Thiago Jung Bauermann
[not found] ` <20170901202743.9678-1-bauerman-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-09-03 0:49 ` Michael Kerrisk (man-pages)
[not found] ` <07aa1031-91b5-f1ca-b23f-858c06c3a9f8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-03 2:24 ` Thiago Jung Bauermann [this message]
[not found] ` <87fuc4semh.fsf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-09-03 11:32 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuc4semh.fsf@linux.vnet.ibm.com \
--to=bauerman-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.