Bug 161321 - renice man page gives incorrect usage instruction
renice man page gives incorrect usage instruction
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: man-pages (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jiri Ryska
Ben Levenson
:
: 161462 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-22 09:01 EDT by Charles R. Price, Jr.
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: man-pages-2.05-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-04 10:56:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Charles R. Price, Jr. 2005-06-22 09:01:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
The renice man page installed at /usr/share/man/man1p/renice.1p.gz calls for a
-n parameter as follows:
renice -n increment [-g | -p | -u] ID ...

This differs from, and precedes in search order, the util-linux-2.12p man page at /usr/share/man/man8/renice.8.gz which gives the following synopsis:
renice priority [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]

The major difference is the -n parameter called for in the man-pages instruction, but not accepted by the util-linux program.

If the -n parameter is used the following error message is returned:

renice: 10: getpriority: No such process
3983: old priority 0, new priority 0


Version-Release number of selected component (if applicable):
man-pages-1.67-7

How reproducible:
Always

Steps to Reproduce:
1.renice -n 10 -p <pid>
2.
3.
  

Actual Results:  renice: 10: getpriority: No such process
3983: old priority 0, new priority 0


Expected Results:  3983: old priority 0, new priority 10

Additional info:
Comment 1 Jiri Ryska 2005-07-14 04:24:14 EDT
*** Bug 161462 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.