From: Alejandro Colomar Date: Sat, 14 May 2022 21:25:42 +0000 (+0200) Subject: getpriority.2: Minor tweaks to Theodore's patch X-Git-Tag: man-pages-5.19-rc1~9 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e89f125dc368550111522897ad57827466f0a3a3;p=thirdparty%2Fman-pages.git getpriority.2: Minor tweaks to Theodore's patch Signed-off-by: Alejandro Colomar --- diff --git a/man2/getpriority.2 b/man2/getpriority.2 index 8970410053..67fd971be2 100644 --- a/man2/getpriority.2 +++ b/man2/getpriority.2 @@ -183,9 +183,12 @@ manner as Linux 2.6.12 and later. .SS C library/kernel differences The getpriority system call returns nice values translated to the range 40..1, since a negative return value would be interpreted as an error. -The glibc wrapper function for getpriority translates the value back according to the formula -.IR "unice\ =\ 20\ \-\ knice" . -(Thus, the 40..1 range returned by the kernel corresponds to the range \-20..19 as seen by user space.) +The glibc wrapper function for +.BR getpriority () +translates the value back according to the formula +.I unice\~=\~20\~\-\~knice +(thus, the 40..1 range returned by the kernel +corresponds to the range \-20..19 as seen by user space). .SH BUGS According to POSIX, the nice value is a per-process setting. However, under the current Linux/NPTL implementation of POSIX threads,