From: Kir Kolyshkin <kolyshkin@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Kir Kolyshkin <kolyshkin@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 05/16] getpriority.2: move info from NOTES to HISTORY
Date: Mon, 17 Jun 2024 16:10:17 -0700 [thread overview]
Message-ID: <20240617231035.1766780-6-kolyshkin@gmail.com> (raw)
In-Reply-To: <20240617231035.1766780-1-kolyshkin@gmail.com>
In the spirit of commit 4131356cd ("man*/, man-pages.7: VERSIONS,
STANDARDS, HISTORY: Reorganize sections"), move the historical
information about EPERM error from NOTES to HISTORY, and fix the
section reference accordingly.
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
man/man2/getpriority.2 | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/man/man2/getpriority.2 b/man/man2/getpriority.2
index 111b591b5..4784407ee 100644
--- a/man/man2/getpriority.2
+++ b/man/man2/getpriority.2
@@ -138,7 +138,7 @@ .SH ERRORS
and was not privileged (on Linux: did not have the
.B CAP_SYS_NICE
capability).
-But see NOTES below.
+But see HISTORY below.
.TP
.B ESRCH
No process was located using the
@@ -151,21 +151,6 @@ .SH STANDARDS
.SH HISTORY
POSIX.1-2001,
SVr4, 4.4BSD (these interfaces first appeared in 4.2BSD).
-.SH NOTES
-For further details on the nice value, see
-.BR sched (7).
-.P
-.IR Note :
-the addition of the "autogroup" feature in Linux 2.6.38 means that
-the nice value no longer has its traditional effect in many circumstances.
-For details, see
-.BR sched (7).
-.P
-A child created by
-.BR fork (2)
-inherits its parent's nice value.
-The nice value is preserved across
-.BR execve (2).
.P
The details on the condition for
.B EPERM
@@ -182,6 +167,21 @@ .SH NOTES
4.3BSD, FreeBSD 4.3, OpenBSD-2.5, ...) behave in the same
manner as Linux 2.6.12 and later.
.\"
+.SH NOTES
+For further details on the nice value, see
+.BR sched (7).
+.P
+.IR Note :
+the addition of the "autogroup" feature in Linux 2.6.38 means that
+the nice value no longer has its traditional effect in many circumstances.
+For details, see
+.BR sched (7).
+.P
+A child created by
+.BR fork (2)
+inherits its parent's nice value.
+The nice value is preserved across
+.BR execve (2).
.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.
--
2.45.2
next prev parent reply other threads:[~2024-06-17 23:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 23:10 [PATCH 00/16] man2: fix wrong/non-existent section references Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 01/16] cacheflush.2: fix section reference Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 02/16] clone.2: fix wrong " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 03/16] execve.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 04/16] gethostname.2: fix " Kir Kolyshkin
2024-06-17 23:10 ` Kir Kolyshkin [this message]
2024-06-17 23:10 ` [PATCH 06/16] gettimeofday.2: fix wrong " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 07/16] ioperm.2: " Kir Kolyshkin
2024-06-18 13:32 ` Alejandro Colomar
2024-06-18 17:35 ` [PATCH v2 " Kir Kolyshkin
2024-06-18 18:49 ` Alejandro Colomar
2024-06-17 23:10 ` [PATCH 08/16] kill.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 09/16] mkdir.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 10/16] mmap.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 11/16] nice.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 12/16] open.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 13/16] readdir.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 14/16] semctl.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 15/16] uname.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 16/16] wait.2: " Kir Kolyshkin
2024-06-18 13:42 ` [PATCH 00/16] man2: fix wrong/non-existent section references Alejandro Colomar
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=20240617231035.1766780-6-kolyshkin@gmail.com \
--to=kolyshkin@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox