f5f4165105
mmap.2: srcfix: FIXME
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 16:07:12 +01:00
eaa8868c7b
strerror.3: srcfix: FIXME
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 16:02:06 +01:00
00d82ce875
open.2: srcfix: FIXME
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 16:02:06 +01:00
97d8fd295f
ptsname.3: Note that ptsname_r() is proposed for future inclusion in POSIX.1
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 16:02:06 +01:00
b078637007
ptsname.3: CONFORMING TO:: clarify that only ptsname() is standardized (so far)
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 16:02:06 +01:00
2904e19a2b
close.2: Further clarify that close() should not be retried after an error
...
See Linus ancient comments re EINTR in
https://lkml.org/lkml/headers/2005/9/10/129
Date Sat, 10 Sep 2005 12:00:01 -0700 (PDT)
From Linus Torvalds <>
Subject Re: [patch 7/7] uml: retry host close() on EINTR
The FreeBSD 11.0 close() man page says similar:
In case of any error except EBADF, the supplied file
descriptor is deallocated and therefore is no longer valid.
For AIX:
http://publib16.boulder.ibm.com/doc_link/en_US/a_doc_lib/libs/basetrf1/close.htm
If the FileDescriptor parameter refers to a device and the
close subroutine actually results in a device close, and the
device close routine returns an error, the error is returned
to the application. However, the FileDescriptor parameter is
considered closed and it may not be used in any subsequent
calls.
See also:
http://austingroupbugs.net/view.php?id=529
and in particular:
http://austingroupbugs.net/view.php?id=529#c1200
Reported-by: Daniel Wagner <wagi@monom.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 16:02:06 +01:00
2f3db2a58f
symlink.7: SEE ALSO: add namei(1)
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:31:37 +01:00
def79251d4
credentials.7: SEE ALSO: add shadow(5)
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:28:21 +01:00
540038a17d
nice.2: Move discussion of handling the -1 success return to RETURN VALUE
...
This detail was rather hidden in NOTES. Also, rework the text
a little.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
226f6909f0
nice.2: CONFORMING TO: Remove an ancient SVr4 detail on errno values
...
At this stage, vague details (when does EINVAL get returned?) of
ancient implementations are little more than noise in the page.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
32ff480294
nice.2: Rework discussion of nice() return value and standards conformance
...
Make the text a little clearer. In particular, clarify that the
raw system call (still) returns 0 on success.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
52694f0979
nice.2: Add mention of RLIMIT_NICE
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
360c190092
signal.7: tfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
384c705b19
getrlimit.2: Refer to sched(7) in discussion of RLIMIT_RTPRIO and RLIMIT_RTTIME
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
a67b298f5c
getrlimit.2: SEE ALSO: add credentials(7)
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
dfc3c7dedc
getrlimit.2: refer to sched(7) in the discussion of RLIMIT_NICE
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
bbc069dd5b
getrlimit.2: Minor wording fix for RLIMIT_NICE
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
d17de8336c
getrlimit.2: Describe the range of the RLIMIT_NICE limit
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
b5bde13cbc
setsid.2: SEE ALSO: add sched(7)
...
List sched(7), because setsid(2) is part of the machinery
of autogrouping.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
998f951bf8
bpf.2: tfix
...
Changed to "will" instead of "with".
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
1af83f4a7a
nice.2: Warn that autogrouping voids the effect of 'nice' in many cases
...
Refer the reader to sched(7) for the details.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
ccc127001c
getpriority.2: Warn that autogrouping voids the effect of 'nice' in many cases
...
Refer the reader to sched(7) for the details.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
b7171b1495
sched.7: Clarify that autogroup defaults on in various distros
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
58543181f8
sched.7: Note command that can be used to modify the autogroup nice value
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-12-05 12:13:33 +01:00
a695d35c98
sched.7: Improve section on nice value and group scheduling
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-30 18:30:54 +01:00
4fbe161bf2
sched.7: Relocate discussion of group scheduling
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-30 18:30:54 +01:00
7ef1473742
sched.7: Clarify details of autogroup nice value
...
Also clarify its interactions with the thread nice value.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-30 18:30:36 +01:00
c49631b7de
sched.7: srcfix: tfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
0cacdedace
sched.7: Further clarify scheduling policies for which autogroup applied
...
Further clarify that autogroup groups only SCHED_OTHER/SCHED_NICE/
SCHED_IDLE processes.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
e92070f8cc
sched.7: Add a subsection on group scheduling
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
e9c1649aa7
sched.7: Tweak description of cgroups overriding autogroup
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
1dd83d2e8f
sched.7: tfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
58627ec0d8
sched.7: Note error that occurs when writing invalid value to /proc/PID/autogroup
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
626dca367b
sched.7: Further clarify details of group scheduling
...
After comments by Mike Galbraith.
Reported-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
c11d067046
sched.7: wfix
...
Reported-by: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
45922aa8d3
sched.7: srcfix: add details to FIXME
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
ee1f3c18a2
sched.7: Rework discussion of autogroups
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
576b74eec2
sched.7: Rework discussion of autogroup nice value
...
Remove the text saying that setting the autogroup nice value
always lowers the group's priority. That was actually a
bug introduced in Linux 4.7.
Also make it clearer that the autogroup nice value has the same
meaning as the nice value set by setpriority(2).
Reported-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
39b35179bc
proc.5: Add pointers to sched(7) for autogroup files
...
sched(7) describes /proc/sys/kernel/sched_autogroup_enabled
and /proc/PID/autogroup.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
ed520068e7
sched.7: Document the autogroup feature
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
40fcb004f0
getpriority.2: The nice value supplied to setpriority() is clamped
...
Note that the nice value supplied to setpriority() is clamped
to the permitted range.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 21:50:15 +01:00
1dc3d91d7b
namespaces.7: srcfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 17:55:08 +01:00
6ad8b4d00c
sched.7: Minor wording fix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-29 07:48:35 +01:00
969b3dd60b
elf.5: Minor fixes
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 22:19:31 +01:00
bdd5d782a1
elf.5: Minor fixes
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 22:17:38 +01:00
51c705cd36
elf(5): Further details on Notes
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 22:13:31 +01:00
bcbb240cf4
sched.7: Minor rewording of discussion of nice value
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 07:06:59 +01:00
31046c3cbd
sched.7: Add nice(2), getpriority(2), and setpriority(2) to API list
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 07:03:26 +01:00
57865ad728
nice.2: Clarify that nice() changes the nice value of the calling *thread*
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 06:58:54 +01:00
268c281777
getpriority.2: Expand discussion of getpriority() return value
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-11-28 06:56:18 +01:00
Michael Kerrisk