From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>, Luca Versari <veluca93@gmail.com>
Subject: [PATCH] core.5: Clarify that RLIMIT_CORE is ignored when piping.
Date: Sun, 11 Dec 2022 18:48:11 +0100 [thread overview]
Message-ID: <20221211174809.10177-1-alx@kernel.org> (raw)
Reported-by: Luca Versari <veluca93@gmail.com>
Closes: <https://bugzilla.kernel.org/show_bug.cgi?id=216648>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
man5/core.5 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/man5/core.5 b/man5/core.5
index be9753250..a354c5a4f 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -67,6 +67,9 @@ .SH DESCRIPTION
.RI ( limit
in
.BR csh (1)).
+However,
+.B RLIMIT_CORE
+will be ignored if the system is configured to pipe core dumps to a program.
.IP \(bu
The binary being executed by the process does not have read
permission enabled.
--
2.38.1
reply other threads:[~2022-12-11 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221211174809.10177-1-alx@kernel.org \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=veluca93@gmail.com \
/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