diff options
Diffstat (limited to 'man2/close_range.2')
| -rw-r--r-- | man2/close_range.2 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/man2/close_range.2 b/man2/close_range.2 index 380a47365..c1e1e1d14 100644 --- a/man2/close_range.2 +++ b/man2/close_range.2 @@ -62,7 +62,7 @@ The following can occur with The number of open file descriptors exceeds the limit specified in .I /proc/sys/fs/nr_open (see -.BR proc (5)). +.MR proc 5 ). This error can occur in situations where that limit was lowered before a call to .BR close_range () @@ -87,7 +87,7 @@ this is sometimes implemented (on Linux) by listing open file descriptors in .I /proc/self/fd/ and calling -.BR close (2) +.MR close 2 on each one. .BR close_range () can take care of this without requiring @@ -127,7 +127,7 @@ the kernel will unshare a new file descriptor table for the caller up to .IR first , copying as few file descriptors as possible. This avoids subsequent -.BR close (2) +.MR close 2 calls entirely; the whole operation is complete once the table is unshared. .SS Closing files on \fBexec\fP @@ -136,12 +136,12 @@ This is particularly useful in cases where multiple .RB pre- exec setup steps risk conflicting with each other. For example, setting up a -.BR seccomp (2) +.MR seccomp 2 profile can conflict with a .BR close_range () call: if the file descriptors are closed before the -.BR seccomp (2) +.MR seccomp 2 profile is set up, the profile setup can't use them itself, or control their closure; @@ -153,7 +153,7 @@ Using .B CLOSE_RANGE_CLOEXEC avoids this: the descriptors can be marked before the -.BR seccomp (2) +.MR seccomp 2 profile is set up, and the profile can control access to .BR close_range () @@ -194,7 +194,7 @@ $ \fB./a.out /tmp/a /tmp/b /tmp/c\fP Note that the lines showing the pathname .I /proc/9005/fd result from the calls to -.BR opendir (3). +.MR opendir 3 . .SS Program source \& .\" SRC BEGIN (close_range.c) @@ -270,4 +270,4 @@ main(int argc, char *argv[]) .EE .\" SRC END .SH SEE ALSO -.BR close (2) +.MR close 2 |