Errors in man pages, here: signal(7): Wrong constants?

Errors in man pages, here: signal(7): Wrong constants?

[Helge Kreutzmann]

Dear manpages maintainers.
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including manpages) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometiems this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a convention
not held up and sometimes we simply do not understand the original.

We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.

Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to translate into
your source format.

Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.

I'm now reporting the errors for your project. As requested, each
issue is sent in an unique mail for easier tracking on your side. If
future reports should use another channel, please let me know.

**

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 "

-- 
      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/

Re: Errors in man pages, here: signal(7): Wrong constants?

[Michael Kerrisk (man-pages)]

On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> Dear manpages maintainers.
> the manpage-l10n project maintains a large number of translations of
> man pages both from a large variety of sources (including manpages) as
> well for a large variety of target languages.
> 
> During their work translators notice different possible issues in the
> original (english) man pages. Sometiems this is a straightforward
> typo, sometimes a hard to read sentence, sometimes this is a convention
> not held up and sometimes we simply do not understand the original.
> 
> We use several distributions as sources and update regularly (at
> least every 2 month). This means we are fairly recent (some
> distributions like archlinux also update frequently) but might miss
> the latest upstream version once a while, so the error might be
> already fixed. We apologize and ask you to close the issue immediately
> if this should be the case, but given the huge volume of projects and
> the very limited number of volunteers we are not able to double check
> each and every issue.
> 
> Secondly we translators see the manpages in the neutral po format,
> i.e. converted and harmonized, but not the original source (be it man,
> groff, xml or other). So we cannot provide a true patch (where
> possible), but only an approximation which you need to translate into
> your source format.
> 
> Finally the issues I'm reporting have accumulated over time and are
> not always discovered by me, so sometimes my description of the
> problem my be a bit limited - do not hesitate to ask so we can clarify
> them.
> 
> I'm now reporting the errors for your project. As requested, each
> issue is sent in an unique mail for easier tracking on your side. If
> future reports should use another channel, please let me know.
> 
> **
> 
> 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,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Re: Errors in man pages, here: signal(7): Wrong constants?

[Helge Kreutzmann]

[-- 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 --]