From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Errors in man pages, here: signal(7): Wrong constants?
Date: Fri, 24 Apr 2020 20:47:04 +0200 [thread overview]
Message-ID: <20200424184704.GB7401@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <0f9c7479-73f3-9913-8e3f-ca726d24c3bb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
Hallo Michael,
On Mon, Apr 20, 2020 at 10:28:41AM +0200, Michael Kerrisk (man-pages) wrote:
> On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> > **
> >
> > POSIX_TRSIG_MAX -> MIN
> >
> > "Starting with version 2.2, Linux supports real-time signals as originally "
> > "defined in the POSIX.1b real-time extensions (and now included in "
> > "POSIX.1-2001). The range of supported real-time signals is defined by the "
> > "macros B<SIGRTMIN> and B<SIGRTMAX>. POSIX.1-2001 requires that an "
> > "implementation support at least B<_POSIX_RTSIG_MAX> (8) real-time signals."
> > --
> >
> > _POSIX_SIGQUEUE_MAX → MIN
> >
> > "According to POSIX, an implementation should permit at least "
> > "B<_POSIX_SIGQUEUE_MAX> (32) real-time signals to be queued to a process. "
> > "However, Linux does things differently. In kernels up to and including "
> > "2.6.7, Linux imposes a system-wide limit on the number of queued real-time "
> > "signals for all processes. This limit can be viewed and (with privilege) "
> > "changed via the I</proc/sys/kernel/rtsig-max> file. A related file, I</proc/"
> > "sys/kernel/rtsig-nr>, can be used to find out how many real-time signals are "
>
> The constants are correct.
>
> Quoting myself: "The use of the string _MAX in the limit names
> defined by SUSv3 can appear confusing, given their description as minimum
> values. The rationale for the names becomes clear when we consider that each
> of these constants defines an upper limit on some resource or feature, and
> the standards are saying that this upper limit must have a certain
> minimum value."
Thanks for the explanation. I added a note in the translators file to
remind him (her?) in the future of this fact.
Greetings
Helge
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-04-24 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: signal(7): Wrong constants? Helge Kreutzmann
2020-04-20 8:28 ` Michael Kerrisk (man-pages)
2020-04-24 18:47 ` Helge Kreutzmann [this message]
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=20200424184704.GB7401@Debian-50-lenny-64-minimal \
--to=debian@helgefjell.de \
--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;
as well as URLs for NNTP newsgroup(s).