From: Lennart Poettering <lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Confusion regarding unit of RLIMIT_RSS
Date: Mon, 9 Nov 2015 17:07:10 +0100 [thread overview]
Message-ID: <20151109160710.GA7322@gardel-login> (raw)
heya,
The man page for setrlimit() claims that RLIMIT_RSS is to be specified
in bytes, but glibc's bits/resources.h claims it was in bytes. My
suspicion is that the header is right, and the man page wrong. But of
course, since the limit has no effect on Linux anyway, maybe this is
not the most important thing to fix, but I thought I'd at least report
the discrepancy here...
Thanks,
Lennart
--
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 reply other threads:[~2015-11-09 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 16:07 Lennart Poettering [this message]
2015-12-17 7:17 ` Confusion regarding unit of RLIMIT_RSS 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=20151109160710.GA7322@gardel-login \
--to=lennart-mdgvqq1h2p+gdvjs77bj7q@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox