Description of problem: Renice does not seem to allow the changing of process priorities. Renice fails with a "setpriority: Operation not permitted" error. Version-Release number of selected component (if applicable): FC2 How reproducible: Always Steps to Reproduce: 1. Find a already running process' PID (i.e. mozilla) 2. renice -n 10 -p PID Actual results: > renice -n 10 -p 8537 renice: 10: setpriority: Operation not permitted 8537: old priority 0, new priority 0 Expected results: A reniced process! ;-) Additional info: There is an additional problem with setpriority(2) which I will report as a bug too.
Use: renice 10 -p ... Man page is wrong, but 'renice --help' output is correct.
The change in syntax doesn't work... > renice -10 -p 1156 renice: 1156: setpriority: Permission denied I've submitted another bug (#125187) showing a failure of setpriority(2). I wonder if these are related. As a side issue, 'top' also fails on "renice"ing.
From the man page: "Only the super-user may lower priorities."
Oops. Should have RTFM a bit closer. Mea culpa. Still there is the problem that renice won't allow an increase in priority as described in the initial bug report.
renice is functioning correctly for me. The problem is that the man page is incorrect.
The renice man page doesn't mention a -n option, so everything looks correct except the command line that was used.
I have identified the real problem here and filed it as bug 161462.