Description of problem: renice reports changing of "priority" instead of "nice" value. Version-Release number of selected component (if applicable): coreutils-5.0-24 How reproducible: Always Steps to Reproduce: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 10547 peter 5 -10 117M 117M 117M S < 99.9 11.6 6:03 0 vmware-vmx $ renice +1 10547 10547: old priority 1, new priority 1 PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 10547 peter 16 1 131M 131M 130M S N 82.1 12.9 9:06 0 vmware-vmx Actual Results: "old priority" "new priority", but prioity was changed from 5 to 16, nice value was changed from -10 to 1 (like specified). Expected Results: "old nice value" "new nice value"
Nothing to do with coreutils.
The term 'priority' is used throughout the nice & renice man pages as well. Although you're technically correct, the distinction between priority and nice setting is arcane to most users, and they'll be better served by continuing to have it called 'priority'.