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/