From: Alejandro Colomar <alx@kernel.org>
To: Thomas Orgis <thomas@orgis.org>
Cc: linux-man@vger.kernel.org, Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH 1/2] sigaction.2: HISTORY: SA_NOCLDSTOP wasn't added in POSIX.1-2001
Date: Tue, 27 Feb 2024 22:15:01 +0100 [thread overview]
Message-ID: <Zd5Q1bPvS5onFlXp@debian> (raw)
In-Reply-To: <5BA9FE20-851A-4074-8BA3-15F2A5BD3C0F@orgis.org>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Hi Thomas,
On Tue, Feb 27, 2024 at 07:12:16PM +0100, Thomas Orgis wrote:
> Am 25. Februar 2024 12:53:15 MEZ schrieb Alejandro Colomar <alx@kernel.org>:
> >It already existed in POSIX.1-1996, according to just a few lines above.
>
> ... it existing in 1990, not 1996? Or is
Oops, I misread. It's my accident in the commit message. :)
>
> >@@ -1020,7 +1020,6 @@ .SH HISTORY
> > POSIX.1-1990 specified only
>
> a typo? I am by no means an expert on POSIX revisions.
> More interesting in this context seems to be the subtle change
> in SA_NOCLDSTOP behaviour with XSI enabled noted in the spec
>
> https://pubs.opengroup.org/onlinepubs/9699919799/functions/sigaction.html
>
> SA_NOCLDSTOP[CX] Do not generate SIGCHLD when children
> stop [XSI] or stopped children continue.
>
> Should this detail be documented, too, for this flag? Get SIGCHLD only
> if continuing, not when stopping unless with XSI?
Yup, I also noticed that. I'm no expert in that, so I would be more
comfortable if you or someone else send a patch.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-27 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 8:57 SA_RESTART and friends as XSI extensions to POSIX.1-2001 < XOPEN_SOURCE >= 600 Thomas Orgis
2024-02-25 11:41 ` Status of SA_NOCLDWAIT in POSIX.1 (was: SA_RESTART and friends as XSI extensions to POSIX.1-2001 < XOPEN_SOURCE >= 600) Alejandro Colomar
2024-02-25 11:53 ` [PATCH 0/2] sigaction.2: HISTORY: Document history of POSIX constants more accurately Alejandro Colomar
2024-02-25 11:53 ` [PATCH 1/2] sigaction.2: HISTORY: SA_NOCLDSTOP wasn't added in POSIX.1-2001 Alejandro Colomar
2024-02-27 18:12 ` Thomas Orgis
2024-02-27 21:15 ` Alejandro Colomar [this message]
2024-02-25 11:53 ` [PATCH 2/2] sigaction.2: HISTORY: Some constants are or were XSI extensions Alejandro Colomar
2024-02-27 18:14 ` Thomas Orgis
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=Zd5Q1bPvS5onFlXp@debian \
--to=alx@kernel.org \
--cc=eblake@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=thomas@orgis.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.