diff options
| author | Michael Kerrisk | 2016-12-09 13:25:20 +0100 |
|---|---|---|
| committer | Karel Zak | 2016-12-09 13:25:20 +0100 |
| commit | f0742932126a5a8c222776c4a924a02a034f7764 (patch) | |
| tree | 7fb5c7ed7a1d904c1be8c93d8e4a51c9d2aee1e1 /term-utils/agetty.8 | |
| parent | hwclock: don't check for permissions (diff) | |
| download | kernel-qcow2-util-linux-f0742932126a5a8c222776c4a924a02a034f7764.tar.gz kernel-qcow2-util-linux-f0742932126a5a8c222776c4a924a02a034f7764.tar.xz kernel-qcow2-util-linux-f0742932126a5a8c222776c4a924a02a034f7764.zip | |
docs: renice(1): Rework discussion of unprivileged users,
The BUGS section describing the limitations on what an unprivileged
user may do to the nice value is outdated, given the kernel changes
that added RLIMIT_NICE in Linux 2.6.12. So, remove that text.
The revised details for modern Linux were partially covered in NOTES,
but there were also inaccuracies there (and the use of the word
"monotonically" was unneeded). In particular, the point is that
unprivileged users can only increase the nice value. There is no
restriction particular to the range 0..+19. So, for example, the
following scenario is possible:
1. Superuser sets the nice value of an unprivileged user's
process to -20.
2. The unprivileged user can now renice that process to (say) -10.
Signed-off-by: Michael Kerrisk <mtk.man-pages@gmail.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'term-utils/agetty.8')
0 files changed, 0 insertions, 0 deletions