summaryrefslogtreecommitdiffstats
path: root/man5/proc_sys_fs.5
diff options
context:
space:
mode:
Diffstat (limited to 'man5/proc_sys_fs.5')
-rw-r--r--man5/proc_sys_fs.554
1 files changed, 28 insertions, 26 deletions
diff --git a/man5/proc_sys_fs.5 b/man5/proc_sys_fs.5
index e745a64fd..b5149480f 100644
--- a/man5/proc_sys_fs.5
+++ b/man5/proc_sys_fs.5
@@ -17,14 +17,14 @@ related to filesystems.
.IR /proc/sys/fs/aio\-max\-nr " and " /proc/sys/fs/aio\-nr " (since Linux 2.6.4)"
.I aio\-nr
is the running total of the number of events specified by
-.BR io_setup (2)
+.MR io_setup 2
calls for all currently active AIO contexts.
If
.I aio\-nr
reaches
.IR aio\-max\-nr ,
then
-.BR io_setup (2)
+.MR io_setup 2
will fail with the error
.BR EAGAIN .
Raising
@@ -74,7 +74,7 @@ dcache isn't pruned yet.
This file can be used to disable or enable the
.I dnotify
interface described in
-.BR fcntl (2)
+.MR fcntl 2
on a system-wide basis.
A value of 0 in this file disables the interface,
and a value of 1 enables it.
@@ -97,7 +97,7 @@ which can be used to limit the amount of kernel memory consumed by the
.I epoll
interface.
For further details, see
-.BR epoll (7).
+.MR epoll 7 .
.TP
.I /proc/sys/fs/file\-max
This file defines
@@ -105,7 +105,7 @@ a system-wide limit on the number of open files for all processes.
System calls that fail when encountering this limit fail with the error
.BR ENFILE .
(See also
-.BR setrlimit (2),
+.MR setrlimit 2 ,
which can be used by a process to set the per-process limit,
.BR RLIMIT_NOFILE ,
on the number of files it may open.)
@@ -131,7 +131,7 @@ limit.
This (read-only) file contains three numbers:
the number of allocated file handles
(i.e., the number of open file descriptions; see
-.BR open (2));
+.MR open 2 );
the number of free file handles;
and the maximum number of file handles (i.e., the same value as
.IR /proc/sys/fs/file\-max ).
@@ -195,12 +195,13 @@ that can be used to limit the amount of kernel memory consumed by the
.I inotify
interface.
For further details, see
-.BR inotify (7).
+.MR inotify 7 .
.TP
.I /proc/sys/fs/lease\-break\-time
This file specifies the grace period that the kernel grants to a process
holding a file lease
-.RB ( fcntl (2))
+\%(\c
+.MR fcntl 2 )
after it has sent a signal to that process notifying it
that another process is waiting to open the file.
If the lease holder does not remove or downgrade the lease within
@@ -208,7 +209,8 @@ this grace period, the kernel forcibly breaks the lease.
.TP
.I /proc/sys/fs/leases\-enable
This file can be used to enable or disable file leases
-.RB ( fcntl (2))
+\%(\c
+.MR fcntl 2 )
on a system-wide basis.
If this file contains the value 0, leases are disabled.
A nonzero value enables leases.
@@ -224,7 +226,7 @@ This directory contains files
.IR msg_max ", " msgsize_max ", and " queues_max ,
controlling the resources used by POSIX message queues.
See
-.BR mq_overview (7)
+.MR mq_overview 7
for details.
.TP
.IR /proc/sys/fs/nr_open " (since Linux 2.6.25)"
@@ -232,7 +234,7 @@ for details.
This file imposes a ceiling on the value to which the
.B RLIMIT_NOFILE
resource limit can be raised (see
-.BR getrlimit (2)).
+.MR getrlimit 2 ).
This ceiling is enforced for both unprivileged and privileged process.
The default value in this file is 1048576.
(Before Linux 2.6.25, the ceiling for
@@ -251,15 +253,15 @@ to the overflow value before being written to disk.
.TP
.IR /proc/sys/fs/pipe\-max\-size " (since Linux 2.6.35)"
See
-.BR pipe (7).
+.MR pipe 7 .
.TP
.IR /proc/sys/fs/pipe\-user\-pages\-hard " (since Linux 4.5)"
See
-.BR pipe (7).
+.MR pipe 7 .
.TP
.IR /proc/sys/fs/pipe\-user\-pages\-soft " (since Linux 4.5)"
See
-.BR pipe (7).
+.MR pipe 7 .
.TP
.IR /proc/sys/fs/protected_fifos " (since Linux 4.19)"
The value in this file is/can be set to one of the following:
@@ -271,7 +273,7 @@ Writing to FIFOs is unrestricted.
1
Don't allow
.B O_CREAT
-.BR open (2)
+.MR open 2
on FIFOs that the caller doesn't own in world-writable sticky directories,
unless the FIFO is owned by the owner of the directory.
.TP
@@ -301,7 +303,7 @@ and the file UID has a mapping in the namespace.
The filesystem UID of the process creating the link matches
the owner (UID) of the target file
(as described in
-.BR credentials (7),
+.MR credentials 7 ,
a process's filesystem UID is normally the same as its effective UID).
.IP \[bu]
All of the following conditions are true:
@@ -344,7 +346,7 @@ Writing to regular files is unrestricted.
1
Don't allow
.B O_CREAT
-.BR open (2)
+.MR open 2
on regular files that the caller doesn't own in
world-writable sticky directories,
unless the regular file is owned by the owner of the directory.
@@ -372,7 +374,7 @@ in the following circumstances:
the filesystem UID of the process following the link matches
the owner (UID) of the symbolic link
(as described in
-.BR credentials (7),
+.MR credentials 7 ,
a process's filesystem UID is normally the same as its effective UID);
.IP \[bu]
the link is not in a sticky world-writable directory; or
@@ -394,7 +396,7 @@ based on time-of-check, time-of-use races when accessing symbolic links.
.\" The following is based on text from Documentation/sysctl/kernel.txt
The value in this file is assigned to a process's "dumpable" flag
in the circumstances described in
-.BR prctl (2).
+.MR prctl 2 .
In effect,
the value in this file determines whether core dump files are
produced for set-user-ID or otherwise protected/tainted binaries.
@@ -410,8 +412,8 @@ Three different integer values can be specified:
This provides the traditional (pre-Linux 2.6.13) behavior.
A core dump will not be produced for a process which has
changed credentials (by calling
-.BR seteuid (2),
-.BR setgid (2),
+.MR seteuid 2 ,
+.MR setgid 2 ,
or similar, or by executing a set-user-ID or set-group-ID program)
or whose binary does not have read permission enabled.
.TP
@@ -419,7 +421,7 @@ or whose binary does not have read permission enabled.
.\" In kernel source: SUID_DUMP_USER
All processes dump core when possible.
(Reasons why a process might nevertheless not dump core are described in
-.BR core (5).)
+.MR core 5 .)
The core dump is owned by the filesystem user ID of the dumping process
and no security is applied.
This is intended for system debugging situations only:
@@ -441,7 +443,7 @@ Additionally, since Linux 3.6,
.I /proc/sys/kernel/core_pattern
must either be an absolute pathname
or a pipe command, as detailed in
-.BR core (5).
+.MR core 5 .
Warnings will be written to the kernel log if
.I core_pattern
does not follow these rules, and no core dump will be produced.
@@ -450,7 +452,7 @@ does not follow these rules, and no core dump will be produced.
.IP
For details of the effect of a process's "dumpable" setting
on ptrace access mode checking, see
-.BR ptrace (2).
+.MR ptrace 2 .
.TP
.I /proc/sys/fs/super\-max
This file
@@ -467,5 +469,5 @@ allows you to.
This file
contains the number of filesystems currently mounted.
.SH SEE ALSO
-.BR proc (5),
-.BR proc_sys (5)
+.MR proc 5 ,
+.MR proc_sys 5