diff options
author | Shen Feng <shen@cn.fujitsu.com> | 2009-04-02 19:57:20 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-04-02 22:04:53 -0400 |
commit | 760df93ecdd59fc1c213a491b5adee79f53606da (patch) | |
tree | 305a4e0fae43549eb24a3ebcf9bcc15a16ef2138 /Documentation/filesystems | |
parent | 70eed8d06601ca3810a0e56035eae6496d57856b (diff) |
documentation: update Documentation/filesystem/proc.txt and Documentation/sysctls
Now /proc/sys is described in many places and much information is
redundant. This patch updates the proc.txt and move the /proc/sys
desciption out to the files in Documentation/sysctls.
Details are:
merge
- 2.1 /proc/sys/fs - File system data
- 2.11 /proc/sys/fs/mqueue - POSIX message queues filesystem
- 2.17 /proc/sys/fs/epoll - Configuration options for the epoll interface
with Documentation/sysctls/fs.txt.
remove
- 2.2 /proc/sys/fs/binfmt_misc - Miscellaneous binary formats
since it's not better then the Documentation/binfmt_misc.txt.
merge
- 2.3 /proc/sys/kernel - general kernel parameters
with Documentation/sysctls/kernel.txt
remove
- 2.5 /proc/sys/dev - Device specific parameters
since it's obsolete the sysfs is used now.
remove
- 2.6 /proc/sys/sunrpc - Remote procedure calls
since it's not better then the Documentation/sysctls/sunrpc.txt
move
- 2.7 /proc/sys/net - Networking stuff
- 2.9 Appletalk
- 2.10 IPX
to newly created Documentation/sysctls/net.txt.
remove
- 2.8 /proc/sys/net/ipv4 - IPV4 settings
since it's not better then the Documentation/networking/ip-sysctl.txt.
add
- Chapter 3 Per-Process Parameters
to descibe /proc/<pid>/xxx parameters.
Signed-off-by: Shen Feng <shen@cn.fujitsu.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "David S. Miller" <davem@davemloft.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/filesystems')
-rw-r--r-- | Documentation/filesystems/proc.txt | 1097 |
1 files changed, 28 insertions, 1069 deletions
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt index efc4fd9f40ce..ce84cfc9eae0 100644 --- a/Documentation/filesystems/proc.txt +++ b/Documentation/filesystems/proc.txt | |||
@@ -5,6 +5,7 @@ | |||
5 | Bodo Bauer <bb@ricochet.net> | 5 | Bodo Bauer <bb@ricochet.net> |
6 | 6 | ||
7 | 2.4.x update Jorge Nerin <comandante@zaralinux.com> November 14 2000 | 7 | 2.4.x update Jorge Nerin <comandante@zaralinux.com> November 14 2000 |
8 | move /proc/sys Shen Feng <shen@cn.fujitsu.com> April 1 2009 | ||
8 | ------------------------------------------------------------------------------ | 9 | ------------------------------------------------------------------------------ |
9 | Version 1.3 Kernel version 2.2.12 | 10 | Version 1.3 Kernel version 2.2.12 |
10 | Kernel version 2.4.0-test11-pre4 | 11 | Kernel version 2.4.0-test11-pre4 |
@@ -26,25 +27,17 @@ Table of Contents | |||
26 | 1.6 Parallel port info in /proc/parport | 27 | 1.6 Parallel port info in /proc/parport |
27 | 1.7 TTY info in /proc/tty | 28 | 1.7 TTY info in /proc/tty |
28 | 1.8 Miscellaneous kernel statistics in /proc/stat | 29 | 1.8 Miscellaneous kernel statistics in /proc/stat |
30 | 1.9 Ext4 file system parameters | ||
29 | 31 | ||
30 | 2 Modifying System Parameters | 32 | 2 Modifying System Parameters |
31 | 2.1 /proc/sys/fs - File system data | 33 | |
32 | 2.2 /proc/sys/fs/binfmt_misc - Miscellaneous binary formats | 34 | 3 Per-Process Parameters |
33 | 2.3 /proc/sys/kernel - general kernel parameters | 35 | 3.1 /proc/<pid>/oom_adj - Adjust the oom-killer score |
34 | 2.4 /proc/sys/vm - The virtual memory subsystem | 36 | 3.2 /proc/<pid>/oom_score - Display current oom-killer score |
35 | 2.5 /proc/sys/dev - Device specific parameters | 37 | 3.3 /proc/<pid>/io - Display the IO accounting fields |
36 | 2.6 /proc/sys/sunrpc - Remote procedure calls | 38 | 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings |
37 | 2.7 /proc/sys/net - Networking stuff | 39 | 3.5 /proc/<pid>/mountinfo - Information about mounts |
38 | 2.8 /proc/sys/net/ipv4 - IPV4 settings | 40 | |
39 | 2.9 Appletalk | ||
40 | 2.10 IPX | ||
41 | 2.11 /proc/sys/fs/mqueue - POSIX message queues filesystem | ||
42 | 2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score | ||
43 | 2.13 /proc/<pid>/oom_score - Display current oom-killer score | ||
44 | 2.14 /proc/<pid>/io - Display the IO accounting fields | ||
45 | 2.15 /proc/<pid>/coredump_filter - Core dump filtering settings | ||
46 | 2.16 /proc/<pid>/mountinfo - Information about mounts | ||
47 | 2.17 /proc/sys/fs/epoll - Configuration options for the epoll interface | ||
48 | 41 | ||
49 | ------------------------------------------------------------------------------ | 42 | ------------------------------------------------------------------------------ |
50 | Preface | 43 | Preface |
@@ -990,1021 +983,24 @@ review the kernel documentation in the directory /usr/src/linux/Documentation. | |||
990 | This chapter is heavily based on the documentation included in the pre 2.2 | 983 | This chapter is heavily based on the documentation included in the pre 2.2 |
991 | kernels, and became part of it in version 2.2.1 of the Linux kernel. | 984 | kernels, and became part of it in version 2.2.1 of the Linux kernel. |
992 | 985 | ||
993 | 2.1 /proc/sys/fs - File system data | 986 | Please see: Documentation/sysctls/ directory for descriptions of these |
994 | ----------------------------------- | ||
995 | |||
996 | This subdirectory contains specific file system, file handle, inode, dentry | ||
997 | and quota information. | ||
998 | |||
999 | Currently, these files are in /proc/sys/fs: | ||
1000 | |||
1001 | dentry-state | ||
1002 | ------------ | ||
1003 | |||
1004 | Status of the directory cache. Since directory entries are dynamically | ||
1005 | allocated and deallocated, this file indicates the current status. It holds | ||
1006 | six values, in which the last two are not used and are always zero. The others | ||
1007 | are listed in table 2-1. | ||
1008 | |||
1009 | |||
1010 | Table 2-1: Status files of the directory cache | ||
1011 | .............................................................................. | ||
1012 | File Content | ||
1013 | nr_dentry Almost always zero | ||
1014 | nr_unused Number of unused cache entries | ||
1015 | age_limit | ||
1016 | in seconds after the entry may be reclaimed, when memory is short | ||
1017 | want_pages internally | ||
1018 | .............................................................................. | ||
1019 | |||
1020 | dquot-nr and dquot-max | ||
1021 | ---------------------- | ||
1022 | |||
1023 | The file dquot-max shows the maximum number of cached disk quota entries. | ||
1024 | |||
1025 | The file dquot-nr shows the number of allocated disk quota entries and the | ||
1026 | number of free disk quota entries. | ||
1027 | |||
1028 | If the number of available cached disk quotas is very low and you have a large | ||
1029 | number of simultaneous system users, you might want to raise the limit. | ||
1030 | |||
1031 | file-nr and file-max | ||
1032 | -------------------- | ||
1033 | |||
1034 | The kernel allocates file handles dynamically, but doesn't free them again at | ||
1035 | this time. | ||
1036 | |||
1037 | The value in file-max denotes the maximum number of file handles that the | ||
1038 | Linux kernel will allocate. When you get a lot of error messages about running | ||
1039 | out of file handles, you might want to raise this limit. The default value is | ||
1040 | 10% of RAM in kilobytes. To change it, just write the new number into the | ||
1041 | file: | ||
1042 | |||
1043 | # cat /proc/sys/fs/file-max | ||
1044 | 4096 | ||
1045 | # echo 8192 > /proc/sys/fs/file-max | ||
1046 | # cat /proc/sys/fs/file-max | ||
1047 | 8192 | ||
1048 | |||
1049 | |||
1050 | This method of revision is useful for all customizable parameters of the | ||
1051 | kernel - simply echo the new value to the corresponding file. | ||
1052 | |||
1053 | Historically, the three values in file-nr denoted the number of allocated file | ||
1054 | handles, the number of allocated but unused file handles, and the maximum | ||
1055 | number of file handles. Linux 2.6 always reports 0 as the number of free file | ||
1056 | handles -- this is not an error, it just means that the number of allocated | ||
1057 | file handles exactly matches the number of used file handles. | ||
1058 | |||
1059 | Attempts to allocate more file descriptors than file-max are reported with | ||
1060 | printk, look for "VFS: file-max limit <number> reached". | ||
1061 | |||
1062 | inode-state and inode-nr | ||
1063 | ------------------------ | ||
1064 | |||
1065 | The file inode-nr contains the first two items from inode-state, so we'll skip | ||
1066 | to that file... | ||
1067 | |||
1068 | inode-state contains two actual numbers and five dummy values. The numbers | ||
1069 | are nr_inodes and nr_free_inodes (in order of appearance). | ||
1070 | |||
1071 | nr_inodes | ||
1072 | ~~~~~~~~~ | ||
1073 | |||
1074 | Denotes the number of inodes the system has allocated. This number will | ||
1075 | grow and shrink dynamically. | ||
1076 | |||
1077 | nr_open | ||
1078 | ------- | ||
1079 | |||
1080 | Denotes the maximum number of file-handles a process can | ||
1081 | allocate. Default value is 1024*1024 (1048576) which should be | ||
1082 | enough for most machines. Actual limit depends on RLIMIT_NOFILE | ||
1083 | resource limit. | ||
1084 | |||
1085 | nr_free_inodes | ||
1086 | -------------- | ||
1087 | |||
1088 | Represents the number of free inodes. Ie. The number of inuse inodes is | ||
1089 | (nr_inodes - nr_free_inodes). | ||
1090 | |||
1091 | aio-nr and aio-max-nr | ||
1092 | --------------------- | ||
1093 | |||
1094 | aio-nr is the running total of the number of events specified on the | ||
1095 | io_setup system call for all currently active aio contexts. If aio-nr | ||
1096 | reaches aio-max-nr then io_setup will fail with EAGAIN. Note that | ||
1097 | raising aio-max-nr does not result in the pre-allocation or re-sizing | ||
1098 | of any kernel data structures. | ||
1099 | |||
1100 | 2.2 /proc/sys/fs/binfmt_misc - Miscellaneous binary formats | ||
1101 | ----------------------------------------------------------- | ||
1102 | |||
1103 | Besides these files, there is the subdirectory /proc/sys/fs/binfmt_misc. This | ||
1104 | handles the kernel support for miscellaneous binary formats. | ||
1105 | |||
1106 | Binfmt_misc provides the ability to register additional binary formats to the | ||
1107 | Kernel without compiling an additional module/kernel. Therefore, binfmt_misc | ||
1108 | needs to know magic numbers at the beginning or the filename extension of the | ||
1109 | binary. | ||
1110 | |||
1111 | It works by maintaining a linked list of structs that contain a description of | ||
1112 | a binary format, including a magic with size (or the filename extension), | ||
1113 | offset and mask, and the interpreter name. On request it invokes the given | ||
1114 | interpreter with the original program as argument, as binfmt_java and | ||
1115 | binfmt_em86 and binfmt_mz do. Since binfmt_misc does not define any default | ||
1116 | binary-formats, you have to register an additional binary-format. | ||
1117 | |||
1118 | There are two general files in binfmt_misc and one file per registered format. | ||
1119 | The two general files are register and status. | ||
1120 | |||
1121 | Registering a new binary format | ||
1122 | ------------------------------- | ||
1123 | |||
1124 | To register a new binary format you have to issue the command | ||
1125 | |||
1126 | echo :name:type:offset:magic:mask:interpreter: > /proc/sys/fs/binfmt_misc/register | ||
1127 | |||
1128 | |||
1129 | |||
1130 | with appropriate name (the name for the /proc-dir entry), offset (defaults to | ||
1131 | 0, if omitted), magic, mask (which can be omitted, defaults to all 0xff) and | ||
1132 | last but not least, the interpreter that is to be invoked (for example and | ||
1133 | testing /bin/echo). Type can be M for usual magic matching or E for filename | ||
1134 | extension matching (give extension in place of magic). | ||
1135 | |||
1136 | Check or reset the status of the binary format handler | ||
1137 | ------------------------------------------------------ | ||
1138 | |||
1139 | If you do a cat on the file /proc/sys/fs/binfmt_misc/status, you will get the | ||
1140 | current status (enabled/disabled) of binfmt_misc. Change the status by echoing | ||
1141 | 0 (disables) or 1 (enables) or -1 (caution: this clears all previously | ||
1142 | registered binary formats) to status. For example echo 0 > status to disable | ||
1143 | binfmt_misc (temporarily). | ||
1144 | |||
1145 | Status of a single handler | ||
1146 | -------------------------- | ||
1147 | |||
1148 | Each registered handler has an entry in /proc/sys/fs/binfmt_misc. These files | ||
1149 | perform the same function as status, but their scope is limited to the actual | ||
1150 | binary format. By cating this file, you also receive all related information | ||
1151 | about the interpreter/magic of the binfmt. | ||
1152 | |||
1153 | Example usage of binfmt_misc (emulate binfmt_java) | ||
1154 | -------------------------------------------------- | ||
1155 | |||
1156 | cd /proc/sys/fs/binfmt_misc | ||
1157 | echo ':Java:M::\xca\xfe\xba\xbe::/usr/local/java/bin/javawrapper:' > register | ||
1158 | echo ':HTML:E::html::/usr/local/java/bin/appletviewer:' > register | ||
1159 | echo ':Applet:M::<!--applet::/usr/local/java/bin/appletviewer:' > register | ||
1160 | echo ':DEXE:M::\x0eDEX::/usr/bin/dosexec:' > register | ||
1161 | |||
1162 | |||
1163 | These four lines add support for Java executables and Java applets (like | ||
1164 | binfmt_java, additionally recognizing the .html extension with no need to put | ||
1165 | <!--applet> to every applet file). You have to install the JDK and the | ||
1166 | shell-script /usr/local/java/bin/javawrapper too. It works around the | ||
1167 | brokenness of the Java filename handling. To add a Java binary, just create a | ||
1168 | link to the class-file somewhere in the path. | ||
1169 | |||
1170 | 2.3 /proc/sys/kernel - general kernel parameters | ||
1171 | ------------------------------------------------ | ||
1172 | |||
1173 | This directory reflects general kernel behaviors. As I've said before, the | ||
1174 | contents depend on your configuration. Here you'll find the most important | ||
1175 | files, along with descriptions of what they mean and how to use them. | ||
1176 | |||
1177 | acct | ||
1178 | ---- | ||
1179 | |||
1180 | The file contains three values; highwater, lowwater, and frequency. | ||
1181 | |||
1182 | It exists only when BSD-style process accounting is enabled. These values | ||
1183 | control its behavior. If the free space on the file system where the log lives | ||
1184 | goes below lowwater percentage, accounting suspends. If it goes above | ||
1185 | highwater percentage, accounting resumes. Frequency determines how often you | ||
1186 | check the amount of free space (value is in seconds). Default settings are: 4, | ||
1187 | 2, and 30. That is, suspend accounting if there is less than 2 percent free; | ||
1188 | resume it if we have a value of 3 or more percent; consider information about | ||
1189 | the amount of free space valid for 30 seconds | ||
1190 | |||
1191 | ctrl-alt-del | ||
1192 | ------------ | ||
1193 | |||
1194 | When the value in this file is 0, ctrl-alt-del is trapped and sent to the init | ||
1195 | program to handle a graceful restart. However, when the value is greater that | ||
1196 | zero, Linux's reaction to this key combination will be an immediate reboot, | ||
1197 | without syncing its dirty buffers. | ||
1198 | |||
1199 | [NOTE] | ||
1200 | When a program (like dosemu) has the keyboard in raw mode, the | ||
1201 | ctrl-alt-del is intercepted by the program before it ever reaches the | ||
1202 | kernel tty layer, and it is up to the program to decide what to do with | ||
1203 | it. | ||
1204 | |||
1205 | domainname and hostname | ||
1206 | ----------------------- | ||
1207 | |||
1208 | These files can be controlled to set the NIS domainname and hostname of your | ||
1209 | box. For the classic darkstar.frop.org a simple: | ||
1210 | |||
1211 | # echo "darkstar" > /proc/sys/kernel/hostname | ||
1212 | # echo "frop.org" > /proc/sys/kernel/domainname | ||
1213 | |||
1214 | |||
1215 | would suffice to set your hostname and NIS domainname. | ||
1216 | |||
1217 | osrelease, ostype and version | ||
1218 | ----------------------------- | ||
1219 | |||
1220 | The names make it pretty obvious what these fields contain: | ||
1221 | |||
1222 | > cat /proc/sys/kernel/osrelease | ||
1223 | 2.2.12 | ||
1224 | |||
1225 | > cat /proc/sys/kernel/ostype | ||
1226 | Linux | ||
1227 | |||
1228 | > cat /proc/sys/kernel/version | ||
1229 | #4 Fri Oct 1 12:41:14 PDT 1999 | ||
1230 | |||
1231 | |||
1232 | The files osrelease and ostype should be clear enough. Version needs a little | ||
1233 | more clarification. The #4 means that this is the 4th kernel built from this | ||
1234 | source base and the date after it indicates the time the kernel was built. The | ||
1235 | only way to tune these values is to rebuild the kernel. | ||
1236 | |||
1237 | panic | ||
1238 | ----- | ||
1239 | |||
1240 | The value in this file represents the number of seconds the kernel waits | ||
1241 | before rebooting on a panic. When you use the software watchdog, the | ||
1242 | recommended setting is 60. If set to 0, the auto reboot after a kernel panic | ||
1243 | is disabled, which is the default setting. | ||
1244 | |||
1245 | printk | ||
1246 | ------ | ||
1247 | |||
1248 | The four values in printk denote | ||
1249 | * console_loglevel, | ||
1250 | * default_message_loglevel, | ||
1251 | * minimum_console_loglevel and | ||
1252 | * default_console_loglevel | ||
1253 | respectively. | ||
1254 | |||
1255 | These values influence printk() behavior when printing or logging error | ||
1256 | messages, which come from inside the kernel. See syslog(2) for more | ||
1257 | information on the different log levels. | ||
1258 | |||
1259 | console_loglevel | ||
1260 | ---------------- | ||
1261 | |||
1262 | Messages with a higher priority than this will be printed to the console. | ||
1263 | |||
1264 | default_message_level | ||
1265 | --------------------- | ||
1266 | |||
1267 | Messages without an explicit priority will be printed with this priority. | ||
1268 | |||
1269 | minimum_console_loglevel | ||
1270 | ------------------------ | ||
1271 | |||
1272 | Minimum (highest) value to which the console_loglevel can be set. | ||
1273 | |||
1274 | default_console_loglevel | ||
1275 | ------------------------ | ||
1276 | |||
1277 | Default value for console_loglevel. | ||
1278 | |||
1279 | sg-big-buff | ||
1280 | ----------- | ||
1281 | |||
1282 | This file shows the size of the generic SCSI (sg) buffer. At this point, you | ||
1283 | can't tune it yet, but you can change it at compile time by editing | ||
1284 | include/scsi/sg.h and changing the value of SG_BIG_BUFF. | ||
1285 | |||
1286 | If you use a scanner with SANE (Scanner Access Now Easy) you might want to set | ||
1287 | this to a higher value. Refer to the SANE documentation on this issue. | ||
1288 | |||
1289 | modprobe | ||
1290 | -------- | ||
1291 | |||
1292 | The location where the modprobe binary is located. The kernel uses this | ||
1293 | program to load modules on demand. | ||
1294 | |||
1295 | unknown_nmi_panic | ||
1296 | ----------------- | ||
1297 | |||
1298 | The value in this file affects behavior of handling NMI. When the value is | ||
1299 | non-zero, unknown NMI is trapped and then panic occurs. At that time, kernel | ||
1300 | debugging information is displayed on console. | ||
1301 | |||
1302 | NMI switch that most IA32 servers have fires unknown NMI up, for example. | ||
1303 | If a system hangs up, try pressing the NMI switch. | ||
1304 | |||
1305 | panic_on_unrecovered_nmi | ||
1306 | ------------------------ | ||
1307 | |||
1308 | The default Linux behaviour on an NMI of either memory or unknown is to continue | ||
1309 | operation. For many environments such as scientific computing it is preferable | ||
1310 | that the box is taken out and the error dealt with than an uncorrected | ||
1311 | parity/ECC error get propogated. | ||
1312 | |||
1313 | A small number of systems do generate NMI's for bizarre random reasons such as | ||
1314 | power management so the default is off. That sysctl works like the existing | ||
1315 | panic controls already in that directory. | ||
1316 | |||
1317 | nmi_watchdog | ||
1318 | ------------ | ||
1319 | |||
1320 | Enables/Disables the NMI watchdog on x86 systems. When the value is non-zero | ||
1321 | the NMI watchdog is enabled and will continuously test all online cpus to | ||
1322 | determine whether or not they are still functioning properly. Currently, | ||
1323 | passing "nmi_watchdog=" parameter at boot time is required for this function | ||
1324 | to work. | ||
1325 | |||
1326 | If LAPIC NMI watchdog method is in use (nmi_watchdog=2 kernel parameter), the | ||
1327 | NMI watchdog shares registers with oprofile. By disabling the NMI watchdog, | ||
1328 | oprofile may have more registers to utilize. | ||
1329 | |||
1330 | msgmni | ||
1331 | ------ | ||
1332 | |||
1333 | Maximum number of message queue ids on the system. | ||
1334 | This value scales to the amount of lowmem. It is automatically recomputed | ||
1335 | upon memory add/remove or ipc namespace creation/removal. | ||
1336 | When a value is written into this file, msgmni's value becomes fixed, i.e. it | ||
1337 | is not recomputed anymore when one of the above events occurs. | ||
1338 | Use auto_msgmni to change this behavior. | ||
1339 | |||
1340 | auto_msgmni | ||
1341 | ----------- | ||
1342 | |||
1343 | Enables/Disables automatic recomputing of msgmni upon memory add/remove or | ||
1344 | upon ipc namespace creation/removal (see the msgmni description above). | ||
1345 | Echoing "1" into this file enables msgmni automatic recomputing. | ||
1346 | Echoing "0" turns it off. | ||
1347 | auto_msgmni default value is 1. | ||
1348 | |||
1349 | |||
1350 | 2.4 /proc/sys/vm - The virtual memory subsystem | ||
1351 | ----------------------------------------------- | ||
1352 | |||
1353 | Please see: Documentation/sysctls/vm.txt for a description of these | ||
1354 | entries. | 987 | entries. |
1355 | 988 | ||
989 | ------------------------------------------------------------------------------ | ||
990 | Summary | ||
991 | ------------------------------------------------------------------------------ | ||
992 | Certain aspects of kernel behavior can be modified at runtime, without the | ||
993 | need to recompile the kernel, or even to reboot the system. The files in the | ||
994 | /proc/sys tree can not only be read, but also modified. You can use the echo | ||
995 | command to write value into these files, thereby changing the default settings | ||
996 | of the kernel. | ||
997 | ------------------------------------------------------------------------------ | ||
1356 | 998 | ||
1357 | 2.5 /proc/sys/dev - Device specific parameters | 999 | ------------------------------------------------------------------------------ |
1358 | ---------------------------------------------- | 1000 | CHAPTER 3: PER-PROCESS PARAMETERS |
1359 | 1001 | ------------------------------------------------------------------------------ | |
1360 | Currently there is only support for CDROM drives, and for those, there is only | ||
1361 | one read-only file containing information about the CD-ROM drives attached to | ||
1362 | the system: | ||
1363 | |||
1364 | >cat /proc/sys/dev/cdrom/info | ||
1365 | CD-ROM information, Id: cdrom.c 2.55 1999/04/25 | ||
1366 | |||
1367 | drive name: sr0 hdb | ||
1368 | drive speed: 32 40 | ||
1369 | drive # of slots: 1 0 | ||
1370 | Can close tray: 1 1 | ||
1371 | Can open tray: 1 1 | ||
1372 | Can lock tray: 1 1 | ||
1373 | Can change speed: 1 1 | ||
1374 | Can select disk: 0 1 | ||
1375 | Can read multisession: 1 1 | ||
1376 | Can read MCN: 1 1 | ||
1377 | Reports media changed: 1 1 | ||
1378 | Can play audio: 1 1 | ||
1379 | |||
1380 | |||
1381 | You see two drives, sr0 and hdb, along with a list of their features. | ||
1382 | |||
1383 | 2.6 /proc/sys/sunrpc - Remote procedure calls | ||
1384 | --------------------------------------------- | ||
1385 | |||
1386 | This directory contains four files, which enable or disable debugging for the | ||
1387 | RPC functions NFS, NFS-daemon, RPC and NLM. The default values are 0. They can | ||
1388 | be set to one to turn debugging on. (The default value is 0 for each) | ||
1389 | |||
1390 | 2.7 /proc/sys/net - Networking stuff | ||
1391 | ------------------------------------ | ||
1392 | |||
1393 | The interface to the networking parts of the kernel is located in | ||
1394 | /proc/sys/net. Table 2-3 shows all possible subdirectories. You may see only | ||
1395 | some of them, depending on your kernel's configuration. | ||
1396 | |||
1397 | |||
1398 | Table 2-3: Subdirectories in /proc/sys/net | ||
1399 | .............................................................................. | ||
1400 | Directory Content Directory Content | ||
1401 | core General parameter appletalk Appletalk protocol | ||
1402 | unix Unix domain sockets netrom NET/ROM | ||
1403 | 802 E802 protocol ax25 AX25 | ||
1404 | ethernet Ethernet protocol rose X.25 PLP layer | ||
1405 | ipv4 IP version 4 x25 X.25 protocol | ||
1406 | ipx IPX token-ring IBM token ring | ||
1407 | bridge Bridging decnet DEC net | ||
1408 | ipv6 IP version 6 | ||
1409 | .............................................................................. | ||
1410 | |||
1411 | We will concentrate on IP networking here. Since AX15, X.25, and DEC Net are | ||
1412 | only minor players in the Linux world, we'll skip them in this chapter. You'll | ||
1413 | find some short info on Appletalk and IPX further on in this chapter. Review | ||
1414 | the online documentation and the kernel source to get a detailed view of the | ||
1415 | parameters for those protocols. In this section we'll discuss the | ||
1416 | subdirectories printed in bold letters in the table above. As default values | ||
1417 | are suitable for most needs, there is no need to change these values. | ||
1418 | |||
1419 | /proc/sys/net/core - Network core options | ||
1420 | ----------------------------------------- | ||
1421 | |||
1422 | rmem_default | ||
1423 | ------------ | ||
1424 | |||
1425 | The default setting of the socket receive buffer in bytes. | ||
1426 | |||
1427 | rmem_max | ||
1428 | -------- | ||
1429 | |||
1430 | The maximum receive socket buffer size in bytes. | ||
1431 | |||
1432 | wmem_default | ||
1433 | ------------ | ||
1434 | |||
1435 | The default setting (in bytes) of the socket send buffer. | ||
1436 | |||
1437 | wmem_max | ||
1438 | -------- | ||
1439 | |||
1440 | The maximum send socket buffer size in bytes. | ||
1441 | |||
1442 | message_burst and message_cost | ||
1443 | ------------------------------ | ||
1444 | |||
1445 | These parameters are used to limit the warning messages written to the kernel | ||
1446 | log from the networking code. They enforce a rate limit to make a | ||
1447 | denial-of-service attack impossible. A higher message_cost factor, results in | ||
1448 | fewer messages that will be written. Message_burst controls when messages will | ||
1449 | be dropped. The default settings limit warning messages to one every five | ||
1450 | seconds. | ||
1451 | |||
1452 | warnings | ||
1453 | -------- | ||
1454 | |||
1455 | This controls console messages from the networking stack that can occur because | ||
1456 | of problems on the network like duplicate address or bad checksums. Normally, | ||
1457 | this should be enabled, but if the problem persists the messages can be | ||
1458 | disabled. | ||
1459 | |||
1460 | netdev_budget | ||
1461 | ------------- | ||
1462 | |||
1463 | Maximum number of packets taken from all interfaces in one polling cycle (NAPI | ||
1464 | poll). In one polling cycle interfaces which are registered to polling are | ||
1465 | probed in a round-robin manner. The limit of packets in one such probe can be | ||
1466 | set per-device via sysfs class/net/<device>/weight . | ||
1467 | |||
1468 | netdev_max_backlog | ||
1469 | ------------------ | ||
1470 | |||
1471 | Maximum number of packets, queued on the INPUT side, when the interface | ||
1472 | receives packets faster than kernel can process them. | ||
1473 | |||
1474 | optmem_max | ||
1475 | ---------- | ||
1476 | |||
1477 | Maximum ancillary buffer size allowed per socket. Ancillary data is a sequence | ||
1478 | of struct cmsghdr structures with appended data. | ||
1479 | |||
1480 | /proc/sys/net/unix - Parameters for Unix domain sockets | ||
1481 | ------------------------------------------------------- | ||
1482 | |||
1483 | There are only two files in this subdirectory. They control the delays for | ||
1484 | deleting and destroying socket descriptors. | ||
1485 | |||
1486 | 2.8 /proc/sys/net/ipv4 - IPV4 settings | ||
1487 | -------------------------------------- | ||
1488 | |||
1489 | IP version 4 is still the most used protocol in Unix networking. It will be | ||
1490 | replaced by IP version 6 in the next couple of years, but for the moment it's | ||
1491 | the de facto standard for the internet and is used in most networking | ||
1492 | environments around the world. Because of the importance of this protocol, | ||
1493 | we'll have a deeper look into the subtree controlling the behavior of the IPv4 | ||
1494 | subsystem of the Linux kernel. | ||
1495 | |||
1496 | Let's start with the entries in /proc/sys/net/ipv4. | ||
1497 | |||
1498 | ICMP settings | ||
1499 | ------------- | ||
1500 | |||
1501 | icmp_echo_ignore_all and icmp_echo_ignore_broadcasts | ||
1502 | ---------------------------------------------------- | ||
1503 | |||
1504 | Turn on (1) or off (0), if the kernel should ignore all ICMP ECHO requests, or | ||
1505 | just those to broadcast and multicast addresses. | ||
1506 | |||
1507 | Please note that if you accept ICMP echo requests with a broadcast/multi\-cast | ||
1508 | destination address your network may be used as an exploder for denial of | ||
1509 | service packet flooding attacks to other hosts. | ||
1510 | |||
1511 | icmp_destunreach_rate, icmp_echoreply_rate, icmp_paramprob_rate and icmp_timeexeed_rate | ||
1512 | --------------------------------------------------------------------------------------- | ||
1513 | |||
1514 | Sets limits for sending ICMP packets to specific targets. A value of zero | ||
1515 | disables all limiting. Any positive value sets the maximum package rate in | ||
1516 | hundredth of a second (on Intel systems). | ||
1517 | |||
1518 | IP settings | ||
1519 | ----------- | ||
1520 | |||
1521 | ip_autoconfig | ||
1522 | ------------- | ||
1523 | |||
1524 | This file contains the number one if the host received its IP configuration by | ||
1525 | RARP, BOOTP, DHCP or a similar mechanism. Otherwise it is zero. | ||
1526 | |||
1527 | ip_default_ttl | ||
1528 | -------------- | ||
1529 | |||
1530 | TTL (Time To Live) for IPv4 interfaces. This is simply the maximum number of | ||
1531 | hops a packet may travel. | ||
1532 | |||
1533 | ip_dynaddr | ||
1534 | ---------- | ||
1535 | |||
1536 | Enable dynamic socket address rewriting on interface address change. This is | ||
1537 | useful for dialup interface with changing IP addresses. | ||
1538 | |||
1539 | ip_forward | ||
1540 | ---------- | ||
1541 | |||
1542 | Enable or disable forwarding of IP packages between interfaces. Changing this | ||
1543 | value resets all other parameters to their default values. They differ if the | ||
1544 | kernel is configured as host or router. | ||
1545 | |||
1546 | ip_local_port_range | ||
1547 | ------------------- | ||
1548 | |||
1549 | Range of ports used by TCP and UDP to choose the local port. Contains two | ||
1550 | numbers, the first number is the lowest port, the second number the highest | ||
1551 | local port. Default is 1024-4999. Should be changed to 32768-61000 for | ||
1552 | high-usage systems. | ||
1553 | |||
1554 | ip_no_pmtu_disc | ||
1555 | --------------- | ||
1556 | |||
1557 | Global switch to turn path MTU discovery off. It can also be set on a per | ||
1558 | socket basis by the applications or on a per route basis. | ||
1559 | |||
1560 | ip_masq_debug | ||
1561 | ------------- | ||
1562 | |||
1563 | Enable/disable debugging of IP masquerading. | ||
1564 | |||
1565 | IP fragmentation settings | ||
1566 | ------------------------- | ||
1567 | |||
1568 | ipfrag_high_trash and ipfrag_low_trash | ||
1569 | -------------------------------------- | ||
1570 | |||
1571 | Maximum memory used to reassemble IP fragments. When ipfrag_high_thresh bytes | ||
1572 | of memory is allocated for this purpose, the fragment handler will toss | ||
1573 | packets until ipfrag_low_thresh is reached. | ||
1574 | |||
1575 | ipfrag_time | ||
1576 | ----------- | ||
1577 | |||
1578 | Time in seconds to keep an IP fragment in memory. | ||
1579 | |||
1580 | TCP settings | ||
1581 | ------------ | ||
1582 | |||
1583 | tcp_ecn | ||
1584 | ------- | ||
1585 | |||
1586 | This file controls the use of the ECN bit in the IPv4 headers. This is a new | ||
1587 | feature about Explicit Congestion Notification, but some routers and firewalls | ||
1588 | block traffic that has this bit set, so it could be necessary to echo 0 to | ||
1589 | /proc/sys/net/ipv4/tcp_ecn if you want to talk to these sites. For more info | ||
1590 | you could read RFC2481. | ||
1591 | |||
1592 | tcp_retrans_collapse | ||
1593 | -------------------- | ||
1594 | |||
1595 | Bug-to-bug compatibility with some broken printers. On retransmit, try to send | ||
1596 | larger packets to work around bugs in certain TCP stacks. Can be turned off by | ||
1597 | setting it to zero. | ||
1598 | |||
1599 | tcp_keepalive_probes | ||
1600 | -------------------- | ||
1601 | |||
1602 | Number of keep alive probes TCP sends out, until it decides that the | ||
1603 | connection is broken. | ||
1604 | |||
1605 | tcp_keepalive_time | ||
1606 | ------------------ | ||
1607 | |||
1608 | How often TCP sends out keep alive messages, when keep alive is enabled. The | ||
1609 | default is 2 hours. | ||
1610 | |||
1611 | tcp_syn_retries | ||
1612 | --------------- | ||
1613 | |||
1614 | Number of times initial SYNs for a TCP connection attempt will be | ||
1615 | retransmitted. Should not be higher than 255. This is only the timeout for | ||
1616 | outgoing connections, for incoming connections the number of retransmits is | ||
1617 | defined by tcp_retries1. | ||
1618 | |||
1619 | tcp_sack | ||
1620 | -------- | ||
1621 | |||
1622 | Enable select acknowledgments after RFC2018. | ||
1623 | |||
1624 | tcp_timestamps | ||
1625 | -------------- | ||
1626 | |||
1627 | Enable timestamps as defined in RFC1323. | ||
1628 | |||
1629 | tcp_stdurg | ||
1630 | ---------- | ||
1631 | |||
1632 | Enable the strict RFC793 interpretation of the TCP urgent pointer field. The | ||
1633 | default is to use the BSD compatible interpretation of the urgent pointer | ||
1634 | pointing to the first byte after the urgent data. The RFC793 interpretation is | ||
1635 | to have it point to the last byte of urgent data. Enabling this option may | ||
1636 | lead to interoperability problems. Disabled by default. | ||
1637 | |||
1638 | tcp_syncookies | ||
1639 | -------------- | ||
1640 | |||
1641 | Only valid when the kernel was compiled with CONFIG_SYNCOOKIES. Send out | ||
1642 | syncookies when the syn backlog queue of a socket overflows. This is to ward | ||
1643 | off the common 'syn flood attack'. Disabled by default. | ||
1644 | |||
1645 | Note that the concept of a socket backlog is abandoned. This means the peer | ||
1646 | may not receive reliable error messages from an over loaded server with | ||
1647 | syncookies enabled. | ||
1648 | |||
1649 | tcp_window_scaling | ||
1650 | ------------------ | ||
1651 | |||
1652 | Enable window scaling as defined in RFC1323. | ||
1653 | |||
1654 | tcp_fin_timeout | ||
1655 | --------------- | ||
1656 | |||
1657 | The length of time in seconds it takes to receive a final FIN before the | ||
1658 | socket is always closed. This is strictly a violation of the TCP | ||
1659 | specification, but required to prevent denial-of-service attacks. | ||
1660 | |||
1661 | tcp_max_ka_probes | ||
1662 | ----------------- | ||
1663 | |||
1664 | Indicates how many keep alive probes are sent per slow timer run. Should not | ||
1665 | be set too high to prevent bursts. | ||
1666 | |||
1667 | tcp_max_syn_backlog | ||
1668 | ------------------- | ||
1669 | |||
1670 | Length of the per socket backlog queue. Since Linux 2.2 the backlog specified | ||
1671 | in listen(2) only specifies the length of the backlog queue of already | ||
1672 | established sockets. When more connection requests arrive Linux starts to drop | ||
1673 | packets. When syncookies are enabled the packets are still answered and the | ||
1674 | maximum queue is effectively ignored. | ||
1675 | |||
1676 | tcp_retries1 | ||
1677 | ------------ | ||
1678 | |||
1679 | Defines how often an answer to a TCP connection request is retransmitted | ||
1680 | before giving up. | ||
1681 | |||
1682 | tcp_retries2 | ||
1683 | ------------ | ||
1684 | |||
1685 | Defines how often a TCP packet is retransmitted before giving up. | ||
1686 | |||
1687 | Interface specific settings | ||
1688 | --------------------------- | ||
1689 | |||
1690 | In the directory /proc/sys/net/ipv4/conf you'll find one subdirectory for each | ||
1691 | interface the system knows about and one directory calls all. Changes in the | ||
1692 | all subdirectory affect all interfaces, whereas changes in the other | ||
1693 | subdirectories affect only one interface. All directories have the same | ||
1694 | entries: | ||
1695 | |||
1696 | accept_redirects | ||
1697 | ---------------- | ||
1698 | |||
1699 | This switch decides if the kernel accepts ICMP redirect messages or not. The | ||
1700 | default is 'yes' if the kernel is configured for a regular host and 'no' for a | ||
1701 | router configuration. | ||
1702 | |||
1703 | accept_source_route | ||
1704 | ------------------- | ||
1705 | |||
1706 | Should source routed packages be accepted or declined. The default is | ||
1707 | dependent on the kernel configuration. It's 'yes' for routers and 'no' for | ||
1708 | hosts. | ||
1709 | |||
1710 | bootp_relay | ||
1711 | ~~~~~~~~~~~ | ||
1712 | |||
1713 | Accept packets with source address 0.b.c.d with destinations not to this host | ||
1714 | as local ones. It is supposed that a BOOTP relay daemon will catch and forward | ||
1715 | such packets. | ||
1716 | |||
1717 | The default is 0, since this feature is not implemented yet (kernel version | ||
1718 | 2.2.12). | ||
1719 | |||
1720 | forwarding | ||
1721 | ---------- | ||
1722 | |||
1723 | Enable or disable IP forwarding on this interface. | ||
1724 | |||
1725 | log_martians | ||
1726 | ------------ | ||
1727 | |||
1728 | Log packets with source addresses with no known route to kernel log. | ||
1729 | |||
1730 | mc_forwarding | ||
1731 | ------------- | ||
1732 | |||
1733 | Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE and a | ||
1734 | multicast routing daemon is required. | ||
1735 | |||
1736 | proxy_arp | ||
1737 | --------- | ||
1738 | |||
1739 | Does (1) or does not (0) perform proxy ARP. | ||
1740 | |||
1741 | rp_filter | ||
1742 | --------- | ||
1743 | |||
1744 | Integer value determines if a source validation should be made. 1 means yes, 0 | ||
1745 | means no. Disabled by default, but local/broadcast address spoofing is always | ||
1746 | on. | ||
1747 | |||
1748 | If you set this to 1 on a router that is the only connection for a network to | ||
1749 | the net, it will prevent spoofing attacks against your internal networks | ||
1750 | (external addresses can still be spoofed), without the need for additional | ||
1751 | firewall rules. | ||
1752 | |||
1753 | secure_redirects | ||
1754 | ---------------- | ||
1755 | |||
1756 | Accept ICMP redirect messages only for gateways, listed in default gateway | ||
1757 | list. Enabled by default. | ||
1758 | |||
1759 | shared_media | ||
1760 | ------------ | ||
1761 | |||
1762 | If it is not set the kernel does not assume that different subnets on this | ||
1763 | device can communicate directly. Default setting is 'yes'. | ||
1764 | |||
1765 | send_redirects | ||
1766 | -------------- | ||
1767 | |||
1768 | Determines whether to send ICMP redirects to other hosts. | ||
1769 | |||
1770 | Routing settings | ||
1771 | ---------------- | ||
1772 | |||
1773 | The directory /proc/sys/net/ipv4/route contains several file to control | ||
1774 | routing issues. | ||
1775 | |||
1776 | error_burst and error_cost | ||
1777 | -------------------------- | ||
1778 | |||
1779 | These parameters are used to limit how many ICMP destination unreachable to | ||
1780 | send from the host in question. ICMP destination unreachable messages are | ||
1781 | sent when we cannot reach the next hop while trying to transmit a packet. | ||
1782 | It will also print some error messages to kernel logs if someone is ignoring | ||
1783 | our ICMP redirects. The higher the error_cost factor is, the fewer | ||
1784 | destination unreachable and error messages will be let through. Error_burst | ||
1785 | controls when destination unreachable messages and error messages will be | ||
1786 | dropped. The default settings limit warning messages to five every second. | ||
1787 | |||
1788 | flush | ||
1789 | ----- | ||
1790 | |||
1791 | Writing to this file results in a flush of the routing cache. | ||
1792 | |||
1793 | gc_elasticity, gc_interval, gc_min_interval_ms, gc_timeout, gc_thresh | ||
1794 | --------------------------------------------------------------------- | ||
1795 | |||
1796 | Values to control the frequency and behavior of the garbage collection | ||
1797 | algorithm for the routing cache. gc_min_interval is deprecated and replaced | ||
1798 | by gc_min_interval_ms. | ||
1799 | |||
1800 | |||
1801 | max_size | ||
1802 | -------- | ||
1803 | |||
1804 | Maximum size of the routing cache. Old entries will be purged once the cache | ||
1805 | reached has this size. | ||
1806 | |||
1807 | redirect_load, redirect_number | ||
1808 | ------------------------------ | ||
1809 | |||
1810 | Factors which determine if more ICPM redirects should be sent to a specific | ||
1811 | host. No redirects will be sent once the load limit or the maximum number of | ||
1812 | redirects has been reached. | ||
1813 | |||
1814 | redirect_silence | ||
1815 | ---------------- | ||
1816 | |||
1817 | Timeout for redirects. After this period redirects will be sent again, even if | ||
1818 | this has been stopped, because the load or number limit has been reached. | ||
1819 | |||
1820 | Network Neighbor handling | ||
1821 | ------------------------- | ||
1822 | |||
1823 | Settings about how to handle connections with direct neighbors (nodes attached | ||
1824 | to the same link) can be found in the directory /proc/sys/net/ipv4/neigh. | ||
1825 | |||
1826 | As we saw it in the conf directory, there is a default subdirectory which | ||
1827 | holds the default values, and one directory for each interface. The contents | ||
1828 | of the directories are identical, with the single exception that the default | ||
1829 | settings contain additional options to set garbage collection parameters. | ||
1830 | |||
1831 | In the interface directories you'll find the following entries: | ||
1832 | |||
1833 | base_reachable_time, base_reachable_time_ms | ||
1834 | ------------------------------------------- | ||
1835 | |||
1836 | A base value used for computing the random reachable time value as specified | ||
1837 | in RFC2461. | ||
1838 | |||
1839 | Expression of base_reachable_time, which is deprecated, is in seconds. | ||
1840 | Expression of base_reachable_time_ms is in milliseconds. | ||
1841 | |||
1842 | retrans_time, retrans_time_ms | ||
1843 | ----------------------------- | ||
1844 | |||
1845 | The time between retransmitted Neighbor Solicitation messages. | ||
1846 | Used for address resolution and to determine if a neighbor is | ||
1847 | unreachable. | ||
1848 | |||
1849 | Expression of retrans_time, which is deprecated, is in 1/100 seconds (for | ||
1850 | IPv4) or in jiffies (for IPv6). | ||
1851 | Expression of retrans_time_ms is in milliseconds. | ||
1852 | |||
1853 | unres_qlen | ||
1854 | ---------- | ||
1855 | |||
1856 | Maximum queue length for a pending arp request - the number of packets which | ||
1857 | are accepted from other layers while the ARP address is still resolved. | ||
1858 | |||
1859 | anycast_delay | ||
1860 | ------------- | ||
1861 | |||
1862 | Maximum for random delay of answers to neighbor solicitation messages in | ||
1863 | jiffies (1/100 sec). Not yet implemented (Linux does not have anycast support | ||
1864 | yet). | ||
1865 | |||
1866 | ucast_solicit | ||
1867 | ------------- | ||
1868 | |||
1869 | Maximum number of retries for unicast solicitation. | ||
1870 | |||
1871 | mcast_solicit | ||
1872 | ------------- | ||
1873 | |||
1874 | Maximum number of retries for multicast solicitation. | ||
1875 | |||
1876 | delay_first_probe_time | ||
1877 | ---------------------- | ||
1878 | |||
1879 | Delay for the first time probe if the neighbor is reachable. (see | ||
1880 | gc_stale_time) | ||
1881 | |||
1882 | locktime | ||
1883 | -------- | ||
1884 | |||
1885 | An ARP/neighbor entry is only replaced with a new one if the old is at least | ||
1886 | locktime old. This prevents ARP cache thrashing. | ||
1887 | |||
1888 | proxy_delay | ||
1889 | ----------- | ||
1890 | |||
1891 | Maximum time (real time is random [0..proxytime]) before answering to an ARP | ||
1892 | request for which we have an proxy ARP entry. In some cases, this is used to | ||
1893 | prevent network flooding. | ||
1894 | |||
1895 | proxy_qlen | ||
1896 | ---------- | ||
1897 | |||
1898 | Maximum queue length of the delayed proxy arp timer. (see proxy_delay). | ||
1899 | |||
1900 | app_solicit | ||
1901 | ---------- | ||
1902 | |||
1903 | Determines the number of requests to send to the user level ARP daemon. Use 0 | ||
1904 | to turn off. | ||
1905 | |||
1906 | gc_stale_time | ||
1907 | ------------- | ||
1908 | |||
1909 | Determines how often to check for stale ARP entries. After an ARP entry is | ||
1910 | stale it will be resolved again (which is useful when an IP address migrates | ||
1911 | to another machine). When ucast_solicit is greater than 0 it first tries to | ||
1912 | send an ARP packet directly to the known host When that fails and | ||
1913 | mcast_solicit is greater than 0, an ARP request is broadcasted. | ||
1914 | |||
1915 | 2.9 Appletalk | ||
1916 | ------------- | ||
1917 | |||
1918 | The /proc/sys/net/appletalk directory holds the Appletalk configuration data | ||
1919 | when Appletalk is loaded. The configurable parameters are: | ||
1920 | |||
1921 | aarp-expiry-time | ||
1922 | ---------------- | ||
1923 | |||
1924 | The amount of time we keep an ARP entry before expiring it. Used to age out | ||
1925 | old hosts. | ||
1926 | |||
1927 | aarp-resolve-time | ||
1928 | ----------------- | ||
1929 | |||
1930 | The amount of time we will spend trying to resolve an Appletalk address. | ||
1931 | |||
1932 | aarp-retransmit-limit | ||
1933 | --------------------- | ||
1934 | |||
1935 | The number of times we will retransmit a query before giving up. | ||
1936 | |||
1937 | aarp-tick-time | ||
1938 | -------------- | ||
1939 | |||
1940 | Controls the rate at which expires are checked. | ||
1941 | |||
1942 | The directory /proc/net/appletalk holds the list of active Appletalk sockets | ||
1943 | on a machine. | ||
1944 | |||
1945 | The fields indicate the DDP type, the local address (in network:node format) | ||
1946 | the remote address, the size of the transmit pending queue, the size of the | ||
1947 | received queue (bytes waiting for applications to read) the state and the uid | ||
1948 | owning the socket. | ||
1949 | |||
1950 | /proc/net/atalk_iface lists all the interfaces configured for appletalk.It | ||
1951 | shows the name of the interface, its Appletalk address, the network range on | ||
1952 | that address (or network number for phase 1 networks), and the status of the | ||
1953 | interface. | ||
1954 | |||
1955 | /proc/net/atalk_route lists each known network route. It lists the target | ||
1956 | (network) that the route leads to, the router (may be directly connected), the | ||
1957 | route flags, and the device the route is using. | ||
1958 | |||
1959 | 2.10 IPX | ||
1960 | -------- | ||
1961 | |||
1962 | The IPX protocol has no tunable values in proc/sys/net. | ||
1963 | |||
1964 | The IPX protocol does, however, provide proc/net/ipx. This lists each IPX | ||
1965 | socket giving the local and remote addresses in Novell format (that is | ||
1966 | network:node:port). In accordance with the strange Novell tradition, | ||
1967 | everything but the port is in hex. Not_Connected is displayed for sockets that | ||
1968 | are not tied to a specific remote address. The Tx and Rx queue sizes indicate | ||
1969 | the number of bytes pending for transmission and reception. The state | ||
1970 | indicates the state the socket is in and the uid is the owning uid of the | ||
1971 | socket. | ||
1972 | |||
1973 | The /proc/net/ipx_interface file lists all IPX interfaces. For each interface | ||
1974 | it gives the network number, the node number, and indicates if the network is | ||
1975 | the primary network. It also indicates which device it is bound to (or | ||
1976 | Internal for internal networks) and the Frame Type if appropriate. Linux | ||
1977 | supports 802.3, 802.2, 802.2 SNAP and DIX (Blue Book) ethernet framing for | ||
1978 | IPX. | ||
1979 | |||
1980 | The /proc/net/ipx_route table holds a list of IPX routes. For each route it | ||
1981 | gives the destination network, the router node (or Directly) and the network | ||
1982 | address of the router (or Connected) for internal networks. | ||
1983 | |||
1984 | 2.11 /proc/sys/fs/mqueue - POSIX message queues filesystem | ||
1985 | ---------------------------------------------------------- | ||
1986 | |||
1987 | The "mqueue" filesystem provides the necessary kernel features to enable the | ||
1988 | creation of a user space library that implements the POSIX message queues | ||
1989 | API (as noted by the MSG tag in the POSIX 1003.1-2001 version of the System | ||
1990 | Interfaces specification.) | ||
1991 | |||
1992 | The "mqueue" filesystem contains values for determining/setting the amount of | ||
1993 | resources used by the file system. | ||
1994 | |||
1995 | /proc/sys/fs/mqueue/queues_max is a read/write file for setting/getting the | ||
1996 | maximum number of message queues allowed on the system. | ||
1997 | |||
1998 | /proc/sys/fs/mqueue/msg_max is a read/write file for setting/getting the | ||
1999 | maximum number of messages in a queue value. In fact it is the limiting value | ||
2000 | for another (user) limit which is set in mq_open invocation. This attribute of | ||
2001 | a queue must be less or equal then msg_max. | ||
2002 | |||
2003 | /proc/sys/fs/mqueue/msgsize_max is a read/write file for setting/getting the | ||
2004 | maximum message size value (it is every message queue's attribute set during | ||
2005 | its creation). | ||
2006 | 1002 | ||
2007 | 2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score | 1003 | 3.1 /proc/<pid>/oom_adj - Adjust the oom-killer score |
2008 | ------------------------------------------------------ | 1004 | ------------------------------------------------------ |
2009 | 1005 | ||
2010 | This file can be used to adjust the score used to select which processes | 1006 | This file can be used to adjust the score used to select which processes |
@@ -2041,25 +1037,15 @@ The task with the highest badness score is then selected and its children | |||
2041 | are killed, process itself will be killed in an OOM situation when it does | 1037 | are killed, process itself will be killed in an OOM situation when it does |
2042 | not have children or some of them disabled oom like described above. | 1038 | not have children or some of them disabled oom like described above. |
2043 | 1039 | ||
2044 | 2.13 /proc/<pid>/oom_score - Display current oom-killer score | 1040 | 3.2 /proc/<pid>/oom_score - Display current oom-killer score |
2045 | ------------------------------------------------------------- | 1041 | ------------------------------------------------------------- |
2046 | 1042 | ||
2047 | ------------------------------------------------------------------------------ | ||
2048 | This file can be used to check the current score used by the oom-killer is for | 1043 | This file can be used to check the current score used by the oom-killer is for |
2049 | any given <pid>. Use it together with /proc/<pid>/oom_adj to tune which | 1044 | any given <pid>. Use it together with /proc/<pid>/oom_adj to tune which |
2050 | process should be killed in an out-of-memory situation. | 1045 | process should be killed in an out-of-memory situation. |
2051 | 1046 | ||
2052 | ------------------------------------------------------------------------------ | ||
2053 | Summary | ||
2054 | ------------------------------------------------------------------------------ | ||
2055 | Certain aspects of kernel behavior can be modified at runtime, without the | ||
2056 | need to recompile the kernel, or even to reboot the system. The files in the | ||
2057 | /proc/sys tree can not only be read, but also modified. You can use the echo | ||
2058 | command to write value into these files, thereby changing the default settings | ||
2059 | of the kernel. | ||
2060 | ------------------------------------------------------------------------------ | ||
2061 | 1047 | ||
2062 | 2.14 /proc/<pid>/io - Display the IO accounting fields | 1048 | 3.3 /proc/<pid>/io - Display the IO accounting fields |
2063 | ------------------------------------------------------- | 1049 | ------------------------------------------------------- |
2064 | 1050 | ||
2065 | This file contains IO statistics for each running process | 1051 | This file contains IO statistics for each running process |
@@ -2161,7 +1147,7 @@ those 64-bit counters, process A could see an intermediate result. | |||
2161 | More information about this can be found within the taskstats documentation in | 1147 | More information about this can be found within the taskstats documentation in |
2162 | Documentation/accounting. | 1148 | Documentation/accounting. |
2163 | 1149 | ||
2164 | 2.15 /proc/<pid>/coredump_filter - Core dump filtering settings | 1150 | 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings |
2165 | --------------------------------------------------------------- | 1151 | --------------------------------------------------------------- |
2166 | When a process is dumped, all anonymous memory is written to a core file as | 1152 | When a process is dumped, all anonymous memory is written to a core file as |
2167 | long as the size of the core file isn't limited. But sometimes we don't want | 1153 | long as the size of the core file isn't limited. But sometimes we don't want |
@@ -2205,7 +1191,7 @@ For example: | |||
2205 | $ echo 0x7 > /proc/self/coredump_filter | 1191 | $ echo 0x7 > /proc/self/coredump_filter |
2206 | $ ./some_program | 1192 | $ ./some_program |
2207 | 1193 | ||
2208 | 2.16 /proc/<pid>/mountinfo - Information about mounts | 1194 | 3.5 /proc/<pid>/mountinfo - Information about mounts |
2209 | -------------------------------------------------------- | 1195 | -------------------------------------------------------- |
2210 | 1196 | ||
2211 | This file contains lines of the form: | 1197 | This file contains lines of the form: |
@@ -2242,30 +1228,3 @@ For more information on mount propagation see: | |||
2242 | 1228 | ||
2243 | Documentation/filesystems/sharedsubtree.txt | 1229 | Documentation/filesystems/sharedsubtree.txt |
2244 | 1230 | ||
2245 | 2.17 /proc/sys/fs/epoll - Configuration options for the epoll interface | ||
2246 | -------------------------------------------------------- | ||
2247 | |||
2248 | This directory contains configuration options for the epoll(7) interface. | ||
2249 | |||
2250 | max_user_instances | ||
2251 | ------------------ | ||
2252 | |||
2253 | This is the maximum number of epoll file descriptors that a single user can | ||
2254 | have open at a given time. The default value is 128, and should be enough | ||
2255 | for normal users. | ||
2256 | |||
2257 | max_user_watches | ||
2258 | ---------------- | ||
2259 | |||
2260 | Every epoll file descriptor can store a number of files to be monitored | ||
2261 | for event readiness. Each one of these monitored files constitutes a "watch". | ||
2262 | This configuration option sets the maximum number of "watches" that are | ||
2263 | allowed for each user. | ||
2264 | Each "watch" costs roughly 90 bytes on a 32bit kernel, and roughly 160 bytes | ||
2265 | on a 64bit one. | ||
2266 | The current default value for max_user_watches is the 1/32 of the available | ||
2267 | low memory, divided for the "watch" cost in bytes. | ||
2268 | |||
2269 | |||
2270 | ------------------------------------------------------------------------------ | ||
2271 | |||