From: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: [PATCH v2] man/man7/signal.7: Update definition of SIGCHLD
Date: Sun, 2 Feb 2025 14:03:31 +0100 [thread overview]
Message-ID: <20250202130331.20320-1-arkadiusz@drabczyk.org> (raw)
In-Reply-To: <20250202121112.9911-1-arkadiusz@drabczyk.org>
Link: <https://unix.stackexchange.com/q/790116/72304>
Link: <https://lore.kernel.org/linux-man/Z5U0Wh_KF3Ki62Pk@comp../>
Signed-off-by: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
---
man/man7/signal.7 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/man/man7/signal.7 b/man/man7/signal.7
index dd04c6d1a..83251e071 100644
--- a/man/man7/signal.7
+++ b/man/man7/signal.7
@@ -360,7 +360,8 @@ Linux supports the standard signals listed below.
The second column of the table indicates which standard (if any)
specified the signal: "P1990" indicates that the signal is described
in the original POSIX.1-1990 standard;
-"P2001" indicates that the signal was added in SUSv2 and POSIX.1-2001.
+"P2001" indicates that the signal was added or its definition changed
+in SUSv2 and POSIX.1-2001.
.TS
l c c l
____
@@ -369,7 +370,7 @@ Signal Standard Action Comment
SIGABRT P1990 Core Abort signal from \fBabort\fP(3)
SIGALRM P1990 Term Timer signal from \fBalarm\fP(2)
SIGBUS P2001 Core Bus error (bad memory access)
-SIGCHLD P1990 Ign Child stopped or terminated
+SIGCHLD P2001 Ign Child stopped, terminated, or continued
SIGCLD \- Ign A synonym for \fBSIGCHLD\fP
SIGCONT P1990 Cont Continue if stopped
SIGEMT \- Term Emulator trap
--
2.45.2
next prev parent reply other threads:[~2025-02-02 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 12:11 [PATCH] man/man7/signal.7: Update definition of SIGCHLD Arkadiusz Drabczyk
2025-02-02 12:30 ` Alejandro Colomar
2025-02-02 13:06 ` Arkadiusz Drabczyk
2025-02-02 13:16 ` Alejandro Colomar
2025-02-02 13:03 ` Arkadiusz Drabczyk [this message]
2025-02-02 13:19 ` [PATCH v2] " Alejandro Colomar
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=20250202130331.20320-1-arkadiusz@drabczyk.org \
--to=arkadiusz@drabczyk.org \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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