From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216648] New: man 5 core incorrectly states circumstances in which a core is not produced
Date: Tue, 01 Nov 2022 12:26:03 +0000 [thread overview]
Message-ID: <bug-216648-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216648
Bug ID: 216648
Summary: man 5 core incorrectly states circumstances in which a
core is not produced
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: veluca93@gmail.com
Regression: No
As per title, the `core` manpage states:
There are various circumstances in which a core dump file is not
produced:
[...]
* The RLIMIT_CORE (core file size) or RLIMIT_FSIZE (file size)
resource limits for the process are set to zero; see
getrlimit(2) and the documentation of the shell's ulimit
command (limit in csh(1)).
However, this is not actually correct when core dumps are piped to a program,
as the section below states ...
* The RLIMIT_CORE limit is not enforced for core dumps that are
piped to a program via this mechanism.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-11-01 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 12:26 bugzilla-daemon [this message]
2022-11-01 14:28 ` [Bug 216648] man 5 core incorrectly states circumstances in which a core is not produced bugzilla-daemon
2022-11-01 14:51 ` bugzilla-daemon
2023-01-08 9:37 ` bugzilla-daemon
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=bug-216648-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.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.