diff options
author | Michael Kerrisk | 2016-12-09 13:32:34 +0100 |
---|---|---|
committer | Karel Zak | 2016-12-09 13:32:34 +0100 |
commit | 2acd68e32ae494081440704dda820f79b26cd022 (patch) | |
tree | 4c0557cb2d7af2f02b6b9ff243e561c430bd4638 /sys-utils/fstab.5 | |
parent | docs: renice(1): Rework discussion of unprivileged users, (diff) | |
download | kernel-qcow2-util-linux-2acd68e32ae494081440704dda820f79b26cd022.tar.gz kernel-qcow2-util-linux-2acd68e32ae494081440704dda820f79b26cd022.tar.xz kernel-qcow2-util-linux-2acd68e32ae494081440704dda820f79b26cd022.zip |
docs: renice(1): Remove obsolete BUGS text
Already at least as far back as util-linux 2.2, renice uses
getpriority(2) to fetch the process's old nice value. Thus,
the "problem" discussed in this BUGS note disappeared long ago.
This is trivially demonstrable:
$ sleep 100 &
[1] 24322
$ renice -n 5 24322
24322 (process ID) old priority 0, new priority 5
$ renice -n 10 24322
24322 (process ID) old priority 5, new priority 10
Rather than trying to explain the ancient problem (20 years old?),
just kill this text.
Signed-off-by: Michael Kerrisk <mtk.man-pages@gmail.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'sys-utils/fstab.5')
0 files changed, 0 insertions, 0 deletions