public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: util-linux@vger.kernel.org
Subject: [PATCH] Correct max priority in renice man page
Date: Sat,  8 Feb 2014 13:22:10 -0500	[thread overview]
Message-ID: <1391883730-11767-1-git-send-email-psusi@ubuntu.com> (raw)

The man page stated that the PRIO_MAX is 20.  While this
is correct, the header definition is wrong and the max
value is actually 19.

Signed-off-by: Phillip Susi <psusi@ubuntu.com>
---
 sys-utils/renice.1 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys-utils/renice.1 b/sys-utils/renice.1
index 538687e..9cb50b8 100644
--- a/sys-utils/renice.1
+++ b/sys-utils/renice.1
@@ -86,14 +86,14 @@ PIDs 987 and 32, plus all processes owned by the users daemon and root:
 Users other than the superuser may only alter the priority of processes they
 own, and can only monotonically increase their ``nice value'' (for security
 reasons) within the range 0 to
-.BR PRIO_MAX \ (20),
+.BR PRIO_MAX \ (19),
 unless a nice resource limit is set (Linux 2.6.12 and higher).  The
 superuser may alter the priority of any process and set the priority to any
 value in the range
 .BR PRIO_MIN \ (\-20)
 to
 .BR PRIO_MAX .
-Useful priorities are: 20 (the affected processes will run only when nothing
+Useful priorities are: 19 (the affected processes will run only when nothing
 else in the system wants to), 0 (the ``base'' scheduling priority), anything
 negative (to make things go very fast).
 .SH FILES
-- 
1.8.3.2


             reply	other threads:[~2014-02-08 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 18:22 Phillip Susi [this message]
2014-02-10 18:08 ` [PATCH] Correct max priority in renice man page Karel Zak

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=1391883730-11767-1-git-send-email-psusi@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=util-linux@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