]> git.ipfire.org Git - thirdparty/man-pages.git/blame - man5/proc.5
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=210704
[thirdparty/man-pages.git] / man5 / proc.5
CommitLineData
fea681da
MK
1.\" Copyright (C) 1994, 1995 by Daniel Quinlan (quinlan@yggdrasil.com)
2.\" with networking additions from Alan Cox (A.Cox@swansea.ac.uk)
3.\" and scsi additions from Michael Neuffer (neuffer@mail.uni-mainz.de)
4.\" and sysctl additions from Andries Brouwer (aeb@cwi.nl)
5.\" and System V IPC (as well as various other) additions from
305a0578 6.\" Michael Kerrisk <mtk-manpages@gmx.net>
fea681da
MK
7.\"
8.\" This is free documentation; you can redistribute it and/or
9.\" modify it under the terms of the GNU General Public License as
10.\" published by the Free Software Foundation; either version 2 of
11.\" the License, or (at your option) any later version.
12.\"
13.\" The GNU General Public License's references to "object code"
14.\" and "executables" are to be interpreted as the output of any
15.\" document formatting or typesetting system, including
16.\" intermediate and printed output.
17.\"
18.\" This manual is distributed in the hope that it will be useful,
19.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
20.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
21.\" GNU General Public License for more details.
22.\"
23.\" You should have received a copy of the GNU General Public
24.\" License along with this manual; if not, write to the Free
25.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
26.\" USA.
27.\"
28.\" Modified 1995-05-17 by faith@cs.unc.edu
29.\" Minor changes by aeb and Marty Leisner (leisner@sdsp.mc.xerox.com).
30.\" Modified 1996-04-13, 1996-07-22 by aeb@cwi.nl
31.\" Modified 2001-12-16 by rwhron@earthlink.net
32.\" Modified 2002-07-13 by jbelton@shaw.ca
33.\" Modified 2002-07-22, 2003-05-27, 2004-04-06, 2004-05-25
305a0578 34.\" by Michael Kerrisk <mtk-manpages@gmx.net>
6b05dc38 35.\" Modified 2004-11-17, mtk -- updated notes on /proc/loadavg
70556c17 36.\" Modified 2004-12-01, mtk, rtsig-max and rtsig-nr went away in 2.6.8
fea681da
MK
37.\"
38.TH PROC 5 2004-05-25 "" "Linux Programmer's Manual"
39.SH NAME
40proc \- process information pseudo-filesystem
41
42.SH DESCRIPTION
43The
44.I proc
45filesystem is a pseudo-filesystem which is used as an interface to
46kernel data structures. It is commonly mounted at
47.IR /proc .
48Most of it is read-only, but some files allow kernel variables to be
49changed.
50.LP
51The following outline gives a quick tour through the /proc hierarchy.
52.PD 1
53.TP
54.I /proc/[number]
55There is a numerical subdirectory for each running process; the
56subdirectory is named by the process ID.
57Each such subdirectory contains the following
58pseudo-files and directories.
59.TP
60.I /proc/[number]/cmdline
61This holds the complete command line for the process, unless the whole
62process has been swapped out or the process is a zombie. In
63either of these latter cases, there is nothing in this file: i.e. a
64read on this file will return 0 characters.
65The command line arguments appear in this file as a set of
66null-separated strings, with a further null byte after the last string.
67.TP
68.I /proc/[number]/cwd
69This is a link to the current working directory of the process. To find
70out
71the cwd of process 20, for instance, you can do this:
72
73.br
74.nf
75.ft CW
76cd /proc/20/cwd; /bin/pwd
77.fi
78.ft
79
80Note that the pwd command is often a shell builtin, and might
81not work properly. In bash, you may use pwd -P.
82.TP
83.I /proc/[number]/environ
84This file contains the environment for the process.
85The entries are separated by null characters,
86and there may be a null character at the end.
87Thus, to print out the environment of process 1, you would do:
88
89.br
90.nf
91.ft CW
92(cat /proc/1/environ; echo) | tr "\\000" "\\n"
93.fi
94.ft P
95
96(For a reason why one should want to do this, see
97.BR lilo (8).)
98.TP
99.I /proc/[number]/exe
100Under Linux 2.2 and later, this file is a symbolic link
101containing the actual path name of the executed command.
102This symbolic link can be dereferenced normally - attempting to open
103it will open the executable. You can even type
104.I /proc/[number]/exe
105to run another copy of the same process as [number].
106
107Under Linux 2.0 and earlier
108.I /proc/[number]/exe
109is a pointer to the binary which was executed,
110and appears as a symbolic link. A
111.BR readlink (2)
112call on this file under Linux 2.0 returns a string in the format:
113
114[device]:inode
115
116For example, [0301]:1502 would be inode 1502 on device major 03 (IDE,
117MFM, etc. drives) minor 01 (first partition on the first drive).
118
119.BR find (1)
120with the -inum option can be used to locate the file.
121.TP
122.I /proc/[number]/fd
123This is a subdirectory containing one entry for each file which the
124process has open, named by its file descriptor, and which is a
125symbolic link to the actual file. Thus, 0 is
126standard input, 1 standard output, 2 standard error, etc.
127
128Programs that will take a filename, but will not take the standard
129input, and which write to a file, but will not send their output to
130standard output, can be effectively foiled this way, assuming that -i
131is the flag designating an input file and -o is the flag designating
132an output file:
133.br
134.nf
135
136\f(CWfoobar -i /proc/self/fd/0 -o /proc/self/fd/1 ...\fR
137
138.fi
139.br
140and you have a working filter.
141.\" The following is not true in my tests (MTK):
142.\" Note that this will not work for
143.\" programs that seek on their files, as the files in the fd directory
144.\" are not seekable.
145
146/proc/self/fd/N is approximately the same as /dev/fd/N in some UNIX
147and UNIX-like systems. Most Linux MAKEDEV scripts symbolically link
148/dev/fd to /proc/self/fd, in fact.
149.TP
150.I /proc/[number]/maps
151A file containing the currently mapped memory regions and their access
152permissions.
153
154The format is:
155
156.nf
157.ft CW
158.in 8n
159address perms offset dev inode pathname
16008048000-08056000 r-xp 00000000 03:0c 64593 /usr/sbin/gpm
16108056000-08058000 rw-p 0000d000 03:0c 64593 /usr/sbin/gpm
16208058000-0805b000 rwxp 00000000 00:00 0
16340000000-40013000 r-xp 00000000 03:0c 4165 /lib/ld-2.2.4.so
16440013000-40015000 rw-p 00012000 03:0c 4165 /lib/ld-2.2.4.so
1654001f000-40135000 r-xp 00000000 03:0c 45494 /lib/libc-2.2.4.so
16640135000-4013e000 rw-p 00115000 03:0c 45494 /lib/libc-2.2.4.so
1674013e000-40142000 rw-p 00000000 00:00 0
168bffff000-c0000000 rwxp 00000000 00:00 0
169.ft
170.fi
171.in
172
173where address is the address space in the process that it occupies,
174perms is a set of permissions:
175
176.nf
177.in +5
178r = read
179w = write
180x = execute
181s = shared
182p = private (copy on write)
183.fi
184.in
185
186offset is the offset into the file/whatever, dev is the device
187(major:minor), and inode is the inode on that device. 0 indicates
188that no inode is associated with the memory region, as the case would
189be with bss.
190
191Under Linux 2.0 there is no field giving pathname.
192.TP
193.I /proc/[number]/mem
194This file can be used to access the pages of a process's memory through
195.BR open (2),
196.BR read (2),
197and
198.BR fseek (3).
199.TP
200.I /proc/[number]/root
201Unix and Linux support the idea of a per-process root of the
202filesystem, set by the
203.BR chroot (2)
204system call. This file is a symbolic link that points to the process's
205root directory, and behaves as exe, fd/*, etc. do.
206.TP
207.I /proc/[number]/stat
208Status information about the process. This is used by
209.BR ps (1).
210It is defined in
211.IR /usr/src/linux/fs/proc/array.c "."
212
213The fields, in order, with their proper
214.BR scanf (3)
215format specifiers, are:
216.RS
217.TP
218\fIpid\fP %d
219The process id.
220.TP
221\fIcomm\fP %s
222The filename of the executable, in parentheses. This is visible
223whether or not the executable is swapped out.
224.TP
225\fIstate\fP %c
226One character from the string "RSDZTW" where R is running, S is
227sleeping in an interruptible wait, D is waiting in uninterruptible
228disk sleep, Z is zombie, T is traced or stopped (on a signal),
229and W is paging.
230.TP
231\fIppid\fP %d
232The PID of the parent.
233.TP
234\fIpgrp\fP %d
235The process group ID of the process.
236.TP
237\fIsession\fP %d
238The session ID of the process.
239.TP
240.\" tty_nr needs better explanation.
241\fItty_nr\fP %d
242The tty the process uses.
243.TP
244\fItpgid\fP %d
245.\" This field and following, up to and including wchan added 0.99.1
246The process group ID of the process which currently owns the tty that
247the process is connected to.
248.TP
249\fIflags\fP %lu
250The kernel flags word of the process. For bit meanings,
251see the PF_* defines in
252.IR <linux/sched.h> .
253Details depend on the kernel version.
254.TP
255\fIminflt\fP %lu
256The number of minor faults the process has made which have not
257required loading a memory page from disk.
258.TP
259\fIcminflt\fP %lu
260The number of minor faults that the process's
261waited-for children have made.
262.TP
263\fImajflt\fP %lu
264The number of major faults the process has made which have
265required loading a memory page from disk.
266.TP
267\fIcmajflt\fP %lu
268The number of major faults that the process's
269waited-for children have made.
270.TP
271\fIutime\fP %lu
272The number of jiffies that this process has been scheduled in user
273mode.
274.TP
275\fIstime\fP %lu
276The number of jiffies that this process has been scheduled in kernel
277mode.
278.TP
279\fIcutime\fP %ld
280The number of jiffies that this process's
281waited-for children have been scheduled in user mode. (See also
282.BR times (2).)
283.TP
284\fIcstime\fP %ld
285The number of jiffies that this process's
286waited-for children have been scheduled in kernel mode.
287.TP
288\fIpriority\fP %ld
289The standard nice value, plus fifteen. The value is never negative in
290the kernel.
291.TP
292\fInice\fP %ld
293The nice value ranges from 19 (nicest) to -19 (not nice to others).
294.TP
295.\" .TP
296.\" \fIcounter\fP %ld
297.\" The current maximum size in jiffies of the process's next timeslice,
298.\" or what is currently left of its current timeslice, if it is the
299.\" currently running process.
300.\" .TP
301.\" \fItimeout\fP %u
302.\" The time in jiffies of the process's next timeout.
303\fI0\fP %ld
304This value is hard coded to 0 as a placeholder for a removed field.
305.TP
306\fIitrealvalue\fP %ld
307The time in jiffies before the next SIGALRM is sent to the process
308due to an interval timer.
309.TP
310\fIstarttime\fP %lu
311The time in jiffies the process started after system boot.
312.TP
313\fIvsize\fP %lu
314Virtual memory size in bytes.
315.TP
316\fIrss\fP %ld
317Resident Set Size: number of pages the process has in real memory,
318minus 3 for administrative purposes. This is just the pages which
319count towards text, data, or stack space. This does not include pages
320which have not been demand-loaded in, or which are swapped out.
321.TP
322\fIrlim\fP %lu
323Current limit in bytes on the rss of the process (usually
3244294967295 on i386).
325.TP
326\fIstartcode\fP %lu
327The address above which program text can run.
328.TP
329\fIendcode\fP %lu
330The address below which program text can run.
331.TP
332\fIstartstack\fP %lu
333The address of the start of the stack.
334.TP
335\fIkstkesp\fP %lu
336The current value of esp (stack pointer), as found in the
337kernel stack page for the process.
338.TP
339\fIkstkeip\fP %lu
340The current EIP (instruction pointer).
341.TP
342\fIsignal\fP %lu
343The bitmap of pending signals (usually 0).
344.TP
345\fIblocked\fP %lu
346The bitmap of blocked signals (usually 0, 2 for shells).
347.TP
348\fIsigignore\fP %lu
349The bitmap of ignored signals.
350.TP
351\fIsigcatch\fP %lu
352The bitmap of catched signals.
353.TP
354\fIwchan\fP %lu
355This is the "channel" in which the process is waiting. It is the
356address of a system call, and can be looked up in a namelist if you
357need a textual name. (If you have an up-to-date /etc/psdatabase, then
358try \fIps -l\fP to see the WCHAN field in action.)
359.TP
360\fInswap\fP %lu
361Number of pages swapped - not maintained.
362.TP
363\fIcnswap\fP %lu
364Cumulative \fInswap\fP for child processes.
365.TP
366\fIexit_signal\fP %d
367Signal to be sent to parent when we die.
368.TP
369\fIprocessor\fP %d
370CPU number last executed on.
371.RE
372.TP
373.I /proc/[number]/statm
374Provides information about memory status in pages. The columns are:
375 size total program size
376 resident resident set size
377 share shared pages
378 trs text (code)
379 drs data/stack
380 lrs library
381 dt dirty pages
382.TP
383.I /proc/[number]/status
384Provides much of the information in
385.I /proc/[number]/stat
386and
387.I /proc/[number]/statm
388in a format that's easier for humans to parse.
389.TP
390.I /proc/apm
391Advanced power management version and battery information
392when CONFIG_APM is defined at kernel compilation time.
393.TP
394.I /proc/bus
395Contains subdirectories for installed busses.
396.TP
397.I /proc/bus/pccard
398Subdirectory for pcmcia devices when CONFIG_PCMCIA is set
399at kernel compilation time.
400.TP
401.I /proc/bus/pccard/drivers
402.TP
403.I /proc/bus/pci
404Contains various bus subdirectories and pseudo-files containing
405information about pci busses, installed devices, and device
406drivers. Some of these files are not ASCII.
407.TP
408.I /proc/bus/pci/devices
409Information about pci devices. They may be accessed through
410.BR lspci (8)
411and
412.BR setpci (8).
413.TP
414.I /proc/cmdline
415Arguments passed to the Linux kernel at boot time. Often done via
416a boot manager such as
417.BR lilo (1).
418.TP
419.I /proc/cpuinfo
420This is a collection of CPU and system architecture dependent items,
421for each supported architecture a different list.
422Two common entries are \fIprocessor\fP which gives CPU number and
423\fIbogomips\fP; a system constant that is calculated
424during kernel initialization. SMP machines have information for
425each CPU.
426.TP
427.I /proc/devices
428Text listing of major numbers and device groups. This can be used by
429MAKEDEV scripts for consistency with the kernel.
430.TP
431.IR /proc/diskstats " (since Linux 2.5.69)"
432This file contains disk I/O statistics for each disk device.
433See the kernel source file
434.I Documentation/iostats.txt
435for further information.
436.TP
437.I /proc/dma
438This is a list of the registered \fIISA\fP DMA (direct memory access)
439channels in use.
440.TP
441.I /proc/driver
442Empty subdirectory.
443.TP
444.I /proc/execdomains
445List of the execution domains (ABI personalities).
446.TP
447.I /proc/fb
448Frame buffer information when CONFIG_FB is defined during kernel
449compilation.
450.TP
451.I /proc/filesystems
452A text listing of the filesystems which were compiled into the kernel.
453Incidentally, this is used by
454.BR mount (1)
455to cycle through different filesystems when none is specified.
456.TP
457.I /proc/fs
458Empty subdirectory.
459.TP
460.I /proc/ide
461This directory
462exists on systems with the ide bus. There are directories for each
463ide channel and attached device. Files include:
464
465.nf
466cache buffer size in KB
467capacity number of sectors
468driver driver version
469geometry physical and logical geometry
470identify in hexidecimal
471media media type
472model manufacturer's model number
473settings drive settings
474smart_thresholds in hexidecimal
475smart_values in hexidecimal
476.fi
477
478The
479.BR hdparm (8)
480utility provides access to this information in a friendly format.
481.TP
482.I /proc/interrupts
483This is used to record the number of interrupts per each IRQ on (at
484least) the i386 architechure. Very easy to read formatting, done in
485ASCII.
486.TP
487.I /proc/iomem
488I/O memory map in Linux 2.4.
489.TP
490.I /proc/ioports
491This is a list of currently registered Input-Output port regions that
492are in use.
493.TP
494.IR /proc/kallsyms " (since Linux 2.5.71)"
495This holds the kernel exported symbol definitions used by the
496.BR modules (X)
497tools to dynamically link and bind loadable modules.
498In Linux 2.5.47 and earlier, a similar file with slightly different syntax
499was named
500.IR ksyms .
501.TP
502.I /proc/kcore
503This file represents the physical memory of the system and is stored
504in the ELF core file format. With this pseudo-file, and an unstripped
505kernel (/usr/src/linux/vmlinux) binary, GDB can be used to
506examine the current state of any kernel data structures.
507
508The total length of the file is the size of physical memory (RAM) plus
5094KB.
510.TP
511.I /proc/kmsg
512This file can be used instead of the
513.BR syslog (2)
514system call to read kernel messages. A process must have superuser
515privileges to read this file, and only one process should read this
516file. This file should not be read if a syslog process is running
517which uses the
518.BR syslog (2)
519system call facility to log kernel messages.
520
521Information in this file is retrieved with the
522.BR dmesg (8)
523program.
524.TP
525.IR /proc/ksyms " (Linux 1.1.23-2.5.47)"
526See
527.IR /proc/kallsyms .
528.TP
529.I /proc/loadavg
6b05dc38
MK
530The first three fields in this file are load average figures
531giving the number of jobs in the run queue (state R)
fea681da
MK
532or waiting for disk I/O (state D) averaged over 1, 5, and 15 minutes.
533They are the same as the load average numbers given by
534.BR uptime (1)
535and other programs.
6b05dc38
MK
536The fourth field consists of two numbers separated by a slash (/).
537The first of these is the number of currently executing kernel
538scheduling entities (processes, threads);
539this will be less than or equal to the number of CPUs.
540The value after the slash is the number of kernel scheduling entities
541that currently exist on the system.
542The fifth field is the PID of the process that was most
543recently created on the system.
fea681da
MK
544.TP
545.I /proc/locks
546This file shows current file locks
547.RB ( flock "(2) and " fcntl (2))
548and leases
549.RB ( fcntl (2)).
550.TP
551.I /proc/malloc
552This file is only present if CONFIGDEBUGMALLOC was defined during
553compilation.
554.TP
555.I /proc/meminfo
556This is used by
557.BR free (1)
558to report the amount of free and used memory (both physical and swap)
559on the system as well as the shared memory and buffers used by the
560kernel.
561
562It is in the same format as
563.BR free (1),
564except in bytes rather than KB.
565.TP
566.I /proc/mounts
567This is a list of all the file systems currently mounted on the system.
568The format of this file is documented in
569.IR fstab (5).
570.TP
571.I /proc/modules
572A text list of the modules that have been loaded by the system.
573See also
574.BR lsmod (8).
575.TP
576.I /proc/mtrr
577Memory Type Range Registers.
578See
579.I /usr/src/linux/Documentation/mtrr.txt
580for details.
581.TP
582.I /proc/net
583various net pseudo-files, all of which give the status of some part of
584the networking layer. These files contain ASCII structures and are,
585therefore, readable with cat. However, the standard
586.BR netstat (8)
587suite provides much cleaner access to these files.
588.TP
589.I /proc/net/arp
590This holds an ASCII readable dump of the kernel ARP table used for
591address resolutions. It will show both dynamically learned and
592pre-programmed ARP entries. The format is:
593
594.nf
595.ft CW
596.in 8n
597IP address HW type Flags HW address Mask Device
598192.168.0.50 0x1 0x2 00:50:BF:25:68:F3 * eth0
599192.168.0.250 0x1 0xc 00:00:00:00:00:00 * eth0
600.ft
601.fi
602.in
603
604Here 'IP address' is the IPv4 address of the machine and the 'HW type'
605is the hardware type of the address from RFC 826. The flags are the internal
606flags of the ARP structure (as defined in /usr/include/linux/if_arp.h) and
607the 'HW address' is the data link layer mapping for that IP address if
608it is known.
609.TP
610.I /proc/net/dev
611The dev pseudo-file contains network device status information. This gives
612the number of received and sent packets, the number of errors and
613collisions
614and other basic statistics. These are used by the
615.BR ifconfig (8)
616program to report device status. The format is:
617
618.nf
619.ft CW
620.in 1n
621Inter-| Receive | Transmit
622 face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
623 lo: 2776770 11307 0 0 0 0 0 0 2776770 11307 0 0 0 0 0 0
624 eth0: 1215645 2751 0 0 0 0 0 0 1782404 4324 0 0 0 427 0 0
625 ppp0: 1622270 5552 1 0 0 0 0 0 354130 5669 0 0 0 0 0 0
626 tap0: 7714 81 0 0 0 0 0 0 7714 81 0 0 0 0 0 0
627.in
628.ft
629.fi
630.\" .TP
631.\" .I /proc/net/ipx
632.\" No information.
633.\" .TP
634.\" .I /proc/net/ipx_route
635.\" No information.
636.TP
637.I /proc/net/dev_mcast
638Defined in
639.IR /usr/src/linux/net/core/dev_mcast.c :
640.nf
641.in +5
642indx ifterface_name dmi_u dmi_g dmi_address
6432 eth0 1 0 01005e000001
6443 eth1 1 0 01005e000001
6454 eth2 1 0 01005e000001
646.in
647.fi
648.TP
649.I /proc/net/igmp
650Internet Group Management Protocol. Defined in
651.IR /usr/src/linux/net/core/igmp.c .
652.TP
653.I /proc/net/rarp
654This file uses the same format as the
655.I arp
656file and contains the current reverse mapping database used to provide
657.BR rarp (8)
658reverse address lookup services. If RARP is not configured into the
659kernel,
660this file will not be present.
661.TP
662.I /proc/net/raw
663Holds a dump of the RAW socket table. Much of the information is not of
664use
665apart from debugging. The 'sl' value is the kernel hash slot for the
666socket,
667the 'local address' is the local address and protocol number pair."St" is
668the internal status of the socket. The "tx_queue" and "rx_queue" are the
669outgoing and incoming data queue in terms of kernel memory usage.
670The "tr", "tm->when", and "rexmits" fields are not used by RAW.
671The uid field holds the creator euid of the socket.
672.\" .TP
673.\" .I /proc/net/route
674.\" No information, but looks similar to
675.\" .BR route (8).
676.TP
677.I /proc/net/snmp
678This file holds the ASCII data needed for the IP, ICMP, TCP, and UDP
679management
680information bases for an snmp agent.
681.TP
682.I /proc/net/tcp
683Holds a dump of the TCP socket table. Much of the information is not
684of use apart from debugging. The "sl" value is the kernel hash slot
685for the socket, the "local address" is the local address and port number pair.
686The "remote address" is the remote address and port number pair
687(if connected). 'St' is the internal status of the socket.
688The 'tx_queue' and 'rx_queue' are the
689outgoing and incoming data queue in terms of kernel memory usage.
690The "tr", "tm->when", and "rexmits" fields hold internal information of
691the kernel socket state and are only useful for debugging. The uid field
692holds the creator euid of the socket.
693.TP
694.I /proc/net/udp
695Holds a dump of the UDP socket table. Much of the information is not of
696use apart from debugging. The "sl" value is the kernel hash slot for the
697socket, the "local address" is the local address and port number pair.
698The "remote address" is the remote address and port number pair
699(if connected). "St" is the internal status of the socket.
700The "tx_queue" and "rx_queue" are the outgoing and incoming data queue
701in terms of kernel memory usage. The "tr", "tm->when", and "rexmits" fields
702are not used by UDP. The uid field holds the creator euid of the socket.
703The format is:
704
705.nf
706.ft CW
707.in 1n
708sl local_address rem_address st tx_queue rx_queue tr rexmits tm->when uid
709 1: 01642C89:0201 0C642C89:03FF 01 00000000:00000001 01:000071BA 00000000 0
710 1: 00000000:0801 00000000:0000 0A 00000000:00000000 00:00000000 6F000100 0
711 1: 00000000:0201 00000000:0000 0A 00000000:00000000 00:00000000 00000000 0
712.in
713.ft
714.fi
715.TP
716.I /proc/net/unix
717Lists the UNIX domain sockets present within the system and their
718status. The format is:
719.nf
720.sp .5
721.ft CW
722Num RefCount Protocol Flags Type St Path
723 0: 00000002 00000000 00000000 0001 03
724 1: 00000001 00000000 00010000 0001 01 /dev/printer
725.ft
726.sp .5
727.fi
728
729Here 'Num' is the kernel table slot number, 'RefCount' is the number
730of users of the socket, 'Protocol' is currently always 0, 'Flags'
731represent the internal kernel flags holding the status of the
732socket. Currently, type is always '1' (Unix domain datagram sockets are
733not yet supported in the kernel). 'St' is the internal state of the
734socket and Path is the bound path (if any) of the socket.
735.TP
736.I /proc/partitions
737Contains major and minor numbers of each partition as well as number
738of blocks and partition name.
739.TP
740.I /proc/pci
741This is a listing of all PCI devices found during kernel initialization
742and their configuration.
743.TP
744.I /proc/scsi
745A directory with the scsi midlevel pseudo-file and various SCSI lowlevel
746driver
747directories, which contain a file for each SCSI host in this system, all
748of
749which give the status of some part of the SCSI IO subsystem.
750These files contain ASCII structures and are, therefore, readable with
751cat.
752
753You can also write to some of the files to reconfigure the subsystem or
754switch
755certain features on or off.
756.TP
757.I /proc/scsi/scsi
758This is a listing of all SCSI devices known to the kernel. The listing is
759similar to the one seen during bootup.
760scsi currently supports only the \fIadd-single-device\fP command which
761allows
762root to add a hotplugged device to the list of known devices.
763
764An
765.B echo 'scsi add-single-device 1 0 5 0' > /proc/scsi/scsi
766will cause
767host scsi1 to scan on SCSI channel 0 for a device on ID 5 LUN 0. If there
768is already a device known on this address or the address is invalid, an
769error will be returned.
770.TP
771.I /proc/scsi/[drivername]
772\fI[drivername]\fP can currently be NCR53c7xx, aha152x, aha1542, aha1740,
773aic7xxx, buslogic, eata_dma, eata_pio, fdomain, in2000, pas16, qlogic,
774scsi_debug, seagate, t128, u15-24f, ultrastore, or wd7000.
775These directories show up for all drivers that registered at least one
776SCSI
777HBA. Every directory contains one file per registered host. Every
778host-file is named after the number the host was assigned during
779initialization.
780
781Reading these files will usually show driver and host configuration,
782statistics etc.
783
784Writing to these files allows different things on different hosts.
785For example, with the \fIlatency\fP and \fInolatency\fP commands,
786root can switch on and off command latency measurement code in the
787eata_dma driver. With the \fIlockup\fP and \fIunlock\fP commands,
788root can control bus lockups simulated by the scsi_debug driver.
789.TP
790.I /proc/self
791This directory refers to the process accessing the /proc filesystem,
792and is identical to the /proc directory named by the process ID of the
793same process.
794.TP
795.I /proc/slabinfo
796Information about kernel caches. The columns are:
797.nf
798cache-name
799num-active-objs
800total-objs
801object-size
802num-active-slabs
803total-slabs
804num-pages-per-slab
805.fi
806See
807.BR slabinfo (5)
808for details.
809.TP
810.I /proc/stat
811kernel/system statistics. Varies with architecture. Common
812entries include:
813.RS
814.TP
815\fIcpu 3357 0 4313 1362393\fP
816The number of jiffies (1/100ths of a second) that the system spent in
817user mode, user mode with low priority (nice), system mode, and the
818idle task, respectively. The last value should be 100 times the
819second entry in the uptime pseudo-file.
820.TP
821\fIpage 5741 1808\fP
822The number of pages the system paged in and the number that were paged
823out (from disk).
824.TP
825\fIswap 1 0\fP
826The number of swap pages that have been brought in and out.
827.TP
828\fIintr 1462898\fP
829The number of interrupts received from the system boot.
830.TP
831\fIdisk_io: (2,0):(31,30,5764,1,2) (3,0):\fP...
832(major,minor):(noinfo, read_io_ops, blks_read, write_io_ops, blks_written)
833.TP
834\fIctxt 115315\fP
835The number of context switches that the system underwent.
836.TP
837\fIbtime 769041601\fP
838boot time, in seconds since the epoch (January 1, 1970).
839.TP
840\fIprocesses 86031\fP
841Number of forks since boot.
842.RE
843.TP
844.I /proc/swaps
845Swap areas in use. See also
846.BR swapon (8).
847.TP
848.I /proc/sys
849This directory (present since 1.3.57) contains a number of files
850and subdirectories corresponding to kernel variables.
851These variables can be read and sometimes modified using
852the \fIproc\fP file system, and the
853.BR sysctl (2)
854system call. Presently, there are subdirectories
855.IR abi ", " debug ", " dev ", " fs ", " kernel ", " net ", " proc ", "
856.IR rxrpc ", " sunrpc " and " vm
857that each contain more files and subdirectories.
858.TP
859.I /proc/sys/abi
860This directory may contain files with application binary information.
861On some systems, it is not present.
862.TP
863.I /proc/sys/debug
864This directory may be empty.
865.TP
866.I /proc/sys/dev
867This directory contains device specific information (eg dev/cdrom/info).
868On
869some systems, it may be empty.
870.TP
871.I /proc/sys/fs
872This contains the subdirectory
873.IR binfmt_misc
874and files
875.IR dentry-state ", " dir-notify-enable ", " dquot-nr ", " file-max ", "
876.IR file-nr ", " inode-max ", " inode-nr ", " inode-state ", "
877.IR lease-break-time ", " leases-enable ", " overflowgid ", " overflowuid
878.IR super-max " and " super-nr
879with function fairly clear from the name.
880.TP
881.I /proc/sys/fs/binfmt_misc
882Documentation for files in this directory can in the kernel sources in
883.IR Documentation/binfmt_misc.txt .
884.TP
885.I /proc/sys/fs/dentry-state
886This file contains six numbers,
887.IR nr_dentry ", " nr_unused ", " age_limit " (age in seconds), "
888want_pages
889(pages requested by system) and two dummy values.
890nr_dentry seems to be 0 all the time.
891nr_unused seems to be the number of unused dentries.
892age_limit is the age in seconds after which dcache entries
893can be reclaimed when memory is short and want_pages is
894nonzero when the kernel has called shrink_dcache_pages() and the
895dcache isn't pruned yet.
896.TP
897.I /proc/sys/fs/dir-notify-enable
898This file can be used to disable or enable the
899.I dnotify
900interface described in
901.BR fcntl (2)
902on a system-wide basis.
903A value of 0 in this file disables the interface,
904and a value of 1 enables it.
905.TP
906.I /proc/sys/fs/dquot-max
907This file shows the maximum number of cached disk quota entries.
908On some (2.4) systems, it is not present.
909If the number of free cached disk quota entries is very low and
910you have some awesome number of simultaneous system users,
911you might want to raise the limit.
912.TP
913.I /proc/sys/fs/dquot-nr
914This file shows the number of allocated disk quota
915entries and the number of free disk quota entries.
916.TP
917.I /proc/sys/fs/file-max
918This file defines
919a system-wide limit on the number of open files for all processes.
920(See also
921.BR setrlimit (2),
922which can be used by a process to set the per-process limit,
923.BR RLIMIT_NOFILE ,
924on the number of files it may open.)
925If you get lots
926of error messages about running out of file handles,
927try increasing this value:
928.br
929
930.br
931.nf
932.ft CW
933echo 100000 > /proc/sys/fs/file-max
934.fi
935.ft
936
937The kernel constant
938.I NR_OPEN
939imposes an upper limit on the value that may be placed in
940.IR file-max .
941
942If you increase
943.IR /proc/sys/fs/file-max ","
944be sure to increase
945.I /proc/sys/fs/inode-max
946to 3-4 times the new
947value of
948.IR /proc/sys/fs/file-max ","
949or you will run out of inodes.
950.TP
951.I /proc/sys/fs/file-nr
952This (read-only) file
953gives the number of files presently opened.
954It contains three numbers: The number of allocated
955file handles, the number of free file handles and the maximum
956number of file handles. The kernel allocates file handles dynamically,
957but it
958doesn't free them again. If the number of allocated files is close to the
959
960maximum, you should consider increasing the maximum.
961When the number of free file handles is
962large, you've encountered a peak in your usage of file
963handles and you probably don't need to increase the maximum.
964.TP
965.I /proc/sys/fs/inode-max
966This file contains the maximum number of in-memory inodes.
967On some (2.4) systems, it may not be
968present. This value should be 3-4 times larger
969than the value in file-max, since stdin, stdout and network sockets also
970need an inode to handle them. When you regularly run
971out of inodes, you need to increase this value.
972.TP
973.I /proc/sys/fs/inode-nr
974This file contains the first two values from inode-state.
975.TP
976.I /proc/sys/fs/inode-state
977This file
978contains seven numbers: nr_inodes, nr_free_inodes, preshrink and four
979dummy
980values.
981nr_inodes is the number of inodes the system has
982allocated. This can be slightly more than inode-max because
983Linux allocates them one pageful at a time.
984nr_free_inodes represents the number of free inodes.
985preshrink is nonzero when the nr_inodes > inode-max and the
986system needs to prune the inode list instead of allocating
987more.
988.TP
989.I /proc/sys/fs/lease-break-time
990This file
991specifies the grace period that the kernel grants to a process
992holding a file lease
993.RB ( fcntl (2))
994after it has sent a signal to that process notifying it
995that another process is waiting to open the file.
996If the lease holder does not remove or downgrade the lease within
997this grace period, the kernel forcibly breaks the lease.
998.TP
999.I /proc/sys/fs/leases-enable
1000This file can be used to enable or disable file leases
1001.RB ( fcntl (2))
1002on a system-wide basis.
1003If this file contains the value 0, leases are disabled.
1004A non-zero value enables leases.
1005.TP
1006.IR /proc/sys/fs/overflowgid " and " /proc/sys/fs/overflowuid
1007These files
1008allow you to change the value of the fixed UID and GID.
1009The default is 65534.
1010Some filesystems only support 16-bit UIDs and GIDs, although in Linux
1011UIDs and GIDs are 32 bits. When one of these filesystems is mounted
1012with writes enabled, any UID or GID that would exceed 65535 is translated
1013to the overflow value before being written to disk.
1014.TP
1015.I /proc/sys/fs/super-max
1016This file
1017controls the maximum number of superblocks, and
1018thus the maximum number of mounted filesystems the kernel
1019can have. You only need to increase super-max if you need to
1020mount more filesystems than the current value in super-max
1021allows you to.
1022.TP
1023.I /proc/sys/fs/super-nr
1024This file
1025contains the number of filesystems currently mounted.
1026.TP
1027.I /proc/sys/kernel
1028This directory contains files
1029.IR acct ", " cad_pid ", " cap-bound ", "
1030.IR core_pattern ", " core_uses_pid ", "
1031.IR ctrl-alt-del ", " dentry-state ", " domainname ", "
1032.IR hotplug ", " hostname ", "
1033.IR htab-reclaim " (PowerPC only), "
1034.IR java-appletviewer " (binfmt_java, obsolete), "
1035.IR java-interpreter " (binfmt_java, obsolete), " l2cr " (PowerPC only), "
1036.IR modprobe ", " msgmax ", " msgmnb ", "
1037.IR msgmni ", " osrelease ", " ostype ", " overflowgid ", " overflowuid ,
1038.IR panic ", " panic_on_oops ", " pid_max ", "
1039.IR powersave-nap " (PowerPC only), " printk ", " pty ", " random ", "
1040.IR real-root-dev ", " reboot-cmd " (SPARC only), " rtsig-max ", "
1041.IR rtsig-nr ", " sem ", " sg-big-buff ", "
1042.IR shmall ", " shmmax ", " shmmni ", " sysrq ", " tainted ", " threads-max ,
1043.IR version " and " zero-paged " (PowerPC only) "
1044with function fairly clear from the name.
1045.TP
1046.I /proc/sys/kernel/acct
1047This file
1048contains three numbers: highwater, lowwater and frequency.
1049If BSD-style process accounting is enabled these values control
1050its behaviour. If free space on filesystem where the log lives
1051goes below lowwater percent accounting suspends. If free space gets
1052above highwater percent accounting resumes. Frequency determines
1053how often the kernel checks the amount of free space (value is in
1054seconds). Default values are 4, 2 and 30.
1055That is, suspend accounting if <= 2% of space is free; resume it
1056if >= 4% of space is free; consider information about amount of free space
1057valid for 30 seconds.
1058.TP
1059.I /proc/sys/kernel/cap-bound
1060This file holds the value of the kernel
1061.IR "capability bounding set"
1062(expressed as a signed decimal number).
1063This set is ANDed against the capabilities permitted to a process
1064during exec.
1065.TP
1066.I /proc/sys/kernel/core_pattern
1067This file
1068(new in Linux 2.5) provides finer control over the form of
1069a core filename than the obsolete
1070.IR /proc/sys/kernel/core_uses_pid
1071file described below.
1072The name for a core file is controlled by defining a template in
1073.IR /proc/sys/kernel/core_pattern .
1074The template can contain % specifiers which are substituted
1075by the following values when a core file is created:
1076.nf
1077
1078 %% A single % character
1079 %p PID of dumped process
1080 %u real UID of dumped process
1081 %g real GID of dumped process
1082 %s number of signal causing dump
1083 %t time of dump (secs since 0:00h, 1 Jan 1970)
1084 %h hostname (same as the 'nodename'
1085 returned by \fBuname\fP(2))
1086 %e executable filename
1087
1088.fi
1089A single % at the end of the template is dropped from the
1090core filename, as is the combination of a % followed by any
1091character other than those listed above.
1092All other characters in the template become a literal
1093part of the core filename.
1094The maximum size of the resulting core filename is 64 bytes.
1095The default value in this file is "core".
1096For backward compatibility, if
1097.I /proc/sys/kernel/core_pattern
1098does not include "%p" and
1099.I /proc/sys/kernel/core_uses_pid
1100is non-zero, then .PID will be appended to the core filename.
1101.TP
1102.I /proc/sys/kernel/core_uses_pid
1103This file
1104can be used control the naming of a core dump file on Linux 2.4.
1105If this file contains the value 0, then a core dump file is simply named
1106.IR core .
1107If this file contains a non-zero value, then the core dump file includes
1108the process ID in a name of the form
1109.IR core.PID .
1110.TP
1111.I /proc/sys/kernel/ctrl-alt-del
1112This file
1113controls the handling of Ctrl-Alt-Del from the keyboard.
1114When the value in this file is 0, Ctrl-Alt-Del is trapped and
1115sent to the
1116.BR init (1)
1117program to handle a graceful restart.
1118When the value is > 0, Linux's reaction to a Vulcan
1119Nerve Pinch (tm) will be an immediate reboot, without even
1120syncing its dirty buffers.
1121Note: when a program (like dosemu) has the keyboard in 'raw'
1122mode, the ctrl-alt-del is intercepted by the program before it
1123ever reaches the kernel tty layer, and it's up to the program
1124to decide what to do with it.
1125.TP
1126.I /proc/sys/kernel/hotplug
1127This file
1128contains the path for the hotplug policy agent.
1129The default value in this file "/sbin/hotplug".
1130.TP
1131.IR /proc/sys/kernel/domainname " and " /proc/sys/kernel/hostname
1132can be used to set the NIS/YP domainname and the
1133hostname of your box in exactly the same way as the commands
1134domainname and hostname, i.e.:
1135.br
1136
1137.br
1138# echo "darkstar" > /proc/sys/kernel/hostname
1139.br
1140# echo "mydomain" > /proc/sys/kernel/domainname
1141.br
1142
1143.br
1144has the same effect as
1145.br
1146
1147.br
1148# hostname "darkstar"
1149.br
1150# domainname "mydomain"
1151.br
1152
1153.br
1154Note, however, that the classic darkstar.frop.org has the
1155hostname "darkstar" and DNS (Internet Domain Name Server)
1156domainname "frop.org", not to be confused with the NIS (Network
1157Information Service) or YP (Yellow Pages) domainname. These two
1158domain names are in general different. For a detailed discussion
1159see the
1160.BR hostname (1)
1161man page.
1162.TP
1163.I /proc/sys/kernel/htab-reclaim
1164(PowerPC only) If this file is set to a non-zero value,
1165the PowerPC htab
1166(see kernel file Documentation/powerpc/ppc_htab.txt) is pruned
1167each time the system hits the idle loop.
1168.TP
1169.I /proc/sys/kernel/l2cr
1170(PowerPC only) This file
1171contains a flag that controls the L2 cache of G3 processor
1172boards. If 0, the cache is disabled. Enabled if nonzero.
1173.TP
1174.I /proc/sys/kernel/modprobe
1175This file
1176is described by the kernel source file Documentation/kmod.txt.
1177.TP
1178.I /proc/sys/kernel/msgmax
1179This file defines
1180a system-wide limit specifying the maximum number of bytes in
1181a single message written on a System V message queue.
1182.TP
1183.I /proc/sys/kernel/msgmni
1184This file defines the system-wide limit on the number of
1185message queue identifiers.
1186(This file is only present in Linux 2.4 onwards.)
1187.TP
1188.I /proc/sys/kernel/msgmnb
1189This file defines a system-wide paramter used to initialise the
1190.I msg_qbytes
1191setting for subsequenly created message queues.
1192The
1193.I msg_qbytes
1194setting specifies the maximum number of bytes that may be written to the
1195message queue.
1196.TP
1197.IR /proc/sys/kernel/ostype " and " /proc/sys/kernel/osrelease
1198These files
1199give substrings of
1200.IR /proc/version .
1201.TP
1202.IR /proc/sys/kernel/overflowgid " and " /proc/sys/kernel/overflowuid
1203These files duplicate the files
1204.I /proc/sys/fs/overflowgid
1205and
1206.IR /proc/sys/fs/overflowuid .
1207.TP
1208.I /proc/sys/kernel/panic
1209gives read/write access to the kernel variable
1210.IR panic_timeout .
1211If this is zero, the kernel will loop on a panic; if nonzero
1212it indicates that the kernel should autoreboot after this number
1213of seconds. When you use the
1214software watchdog device driver, the recommended setting is 60.
1215.TP
1216.I /proc/sys/kernel/panic_on_oops
1217This file (new in Linux 2.5) controls the kernel's behaviour when an oops
1218or
1219BUG is encountered. If this file contains 0, then the system
1220tries to continue operation. If it contains 1, then the system
1221delays a few seconds (to give klogd time to record the oops output)
1222and then panics.
1223If the
1224.I /proc/sys/kernel/panic
1225file is also non-zero then the machine will be rebooted.
1226.TP
1227.I /proc/sys/kernel/pid_max
1228This file
1229(new in Linux 2.5)
1230specifies the value at which PIDs wrap around
1231(i.e., the value in this file is one greater than the maximum PID).
1232The default value for this file, 32768,
1233results in the same range of PIDs as on earlier kernels.
1234The value in this file can be set to any value up to 2^22
1235(PID_MAX_LIMIT, approximately 4 million).
1236.TP
1237.IR /proc/sys/kernel/powersave-nap " (PowerPC only)"
1238This file
1239contains a flag. If set, Linux-PPC will use the 'nap' mode of
1240powersaving,
1241otherwise the 'doze' mode will be used.
1242.TP
1243.I /proc/sys/kernel/printk
1244The four values in this file
1245are console_loglevel, default_message_loglevel, minimum_console_level and
1246default_console_loglevel.
1247These values influence printk() behavior when printing or
1248logging error messages. See
1249.BR syslog (2)
1250for more info on the different loglevels.
1251Messages with a higher priority than
1252console_loglevel will be printed to the console.
1253Messages without an explicit priority
1254will be printed with priority default_message_level.
1255minimum_console_loglevel is the minimum (highest) value to which
1256console_loglevel can be set.
1257default_console_loglevel is the default value for console_loglevel.
1258.TP
1259.IR /proc/sys/kernel/pty " (since Linux 2.6.4)"
1260This directory
1261contains two files relating to the number of Unix 98
1262pseudo-terminals (see
1263.BR pts (4))
1264on the system.
1265.TP
1266.I /proc/sys/kernel/pty/max
1267This file defines the maximum number of pseudo-terminals.
1268.TP
1269.I /proc/sys/kernel/pty/nr
1270This read-only file
1271indicates how many pseudo-terminals are currently in use.
1272.TP
1273.\" FIXME say more about random
1274.I /proc/sys/kernel/random
1275This directory
1276contains various parameters controlling the operation of the file
1277.IR /dev/random .
1278.TP
1279.I /proc/sys/kernel/real-root-dev
1280This file
1281is documented in the kernel source file Documentation/initrd.txt.
1282.TP
1283.IR /proc/sys/kernel/reboot-cmd " (Sparc only) "
1284This file seems to be a way to give an argument to the SPARC
1285ROM/Flash boot loader. Maybe to tell it what to do after
1286rebooting?
1287.TP
1288.I /proc/sys/kernel/rtsig-max
70556c17
MK
1289(Only in kernels up to and including 2.6.7; see
1290.BR setrlimit (2))
fea681da
MK
1291This file can be used to tune the maximum number
1292of POSIX realtime (queued) signals that can be outstanding
1293in the system.
1294.TP
1295.I /proc/sys/kernel/rtsig-nr
70556c17 1296(Only in kernels up to and including 2.6.7.)
fea681da
MK
1297This file shows the number POSIX realtime signals currently queued.
1298.TP
1299.IR /proc/sys/kernel/sem " (since Linux 2.4)"
1300This file contains 4 numbers defining limits for System V IPC semaphores.
1301These fields are, in order:
1302.RS
1303.IP SEMMSL 8
1304The maximum semaphores per semaphore set.
1305.IP SEMMNS 8
1306A system-wide limit on the number of semaphores in all semaphore sets.
1307.IP SEMOPM 8
1308The maximum number of operations that may be specified in a
1309.BR semop (2)
1310call.
1311.IP SEMMNI 8
1312A system-wide limit on the maximum number of semaphore identifiers.
1313.RE
1314.TP
1315.I /proc/sys/kernel/sg-big-buff
1316This file
1317shows the size of the generic SCSI device (sg) buffer.
1318You can't tune it just yet, but you could change it on
1319compile time by editing include/scsi/sg.h and changing
1320the value of SG_BIG_BUFF. However, there shouldn't be any reason to
1321change
1322this value.
1323.TP
1324.I /proc/sys/kernel/shmall
1325This file
1326contains the system-wide limit on the total number of pages of
1327System V shared memory.
1328.TP
1329.I /proc/sys/kernel/shmmax
1330This file
1331can be used to query and set the run time limit
1332on the maximum (System V IPC) shared memory segment size that can be
1333created.
1334Shared memory segments up to 1Gb are now supported in the
1335kernel. This value defaults to SHMMAX.
1336.TP
1337.I /proc/sys/kernel/shmmni
1338(available in Linux 2.4 and onwards)
1339This file
1340specifies the system-wide maximum number of System V shared memory
1341segments that can be created.
1342.TP
1343.I /proc/sys/kernel/version
1344contains a string like:
1345.br
1346
1347.br
1348#5 Wed Feb 25 21:49:24 MET 1998.TP
1349.br
1350
1351.br
1352The '#5' means that
1353this is the fifth kernel built from this source base and the
1354date behind it indicates the time the kernel was built.
1355.TP
1356.IR /proc/sys/kernel/zero-paged " (PowerPC only) "
1357This file
1358contains a flag. When enabled (non-zero), Linux-PPC will pre-zero pages in
1359the idle loop, possibly speeding up get_free_pages.
1360.TP
1361.I /proc/sys/net
1362This directory contains networking stuff.
1363.TP
1364.I /proc/sys/proc
1365This directory may be empty.
1366.TP
1367.I /proc/sys/sunrpc
1368This directory supports Sun remote procedure call for network file system
1369(NFS). On some systems, it is not present.
1370.TP
1371.I /proc/sys/vm
1372This directory contains files for memory management tuning, buffer and
1373cache
1374management.
1375.TP
1376.I /proc/sys/vm/overcommit_memory
1377This file contains the kernel virtual memory accounting mode. Values are:
1378.br
13790: heuristic overcommit (this is the default)
1380.br
13811: always overcommit, never check
1382.br
13832: always check, never overcommit
1384.br
1385In mode 0, calls of
1386.BR mmap (2)
1387with MAP_NORESERVE set are not checked, and the default check is very weak,
1388leading to the risk of getting a process "OOM-killed".
1389Under Linux 2.4 any nonzero value implies mode 1.
1390In mode 2 (available since Linux 2.6), the total virtual address space
1391on the system is limited to (SS + RAM*(r/100)),
1392where SS is the size of the swap space, and RAM
1393is the size of the physical memory, and r is the contents of the file
1394.IR /proc/sys/vm/overcommit_ratio .
1395.TP
1396.I /proc/sys/vm/overcommit_ratio
1397See the description of
1398.IR /proc/sys/vm/overcommit_memory .
1399.TP
1400.I /proc/sysvipc
1401Subdirectory containing the pseudo-files
1402.IR msg ", " sem " and " shm "."
1403These files list the System V Interprocess Communication (IPC) objects
1404(respectively: message queues, semaphores, and shared memory)
1405that currently exist on the system,
1406providing similar information to that available via
1407.BR ipcs (1).
1408These files have headers and are formatted (one IPC object per line)
1409for easy understanding.
1410.BR ipc (5)
1411provides further background on the information shown by these files.
1412.TP
1413.I /proc/tty
1414Subdirectory containing the psuedo-files and subdirectories for
1415tty drivers and line disciplines.
1416.TP
1417.I /proc/uptime
1418This file contains two numbers: the uptime of the system (seconds),
1419and the amount of time spent in idle process (seconds).
1420.TP
1421.I /proc/version
1422This string identifies the kernel version that is currently running.
1423It includes the contents of /proc/sys/ostype, /proc/sys/osrelease and
1424/proc/sys/version. For example:
1425.nf
1426.in -2
1427.ft CW
1428Linux version 1.0.9 (quinlan@phaze) #1 Sat May 14 01:51:54 EDT 1994
1429.ft
1430.in +2
1431.fi
1432.TP
1433.IR /proc/vmstat " (since Linux 2.6)"
1434This file displays various virtual memory statistics.
1435
1436.RE
1437.RE
1438.SH "SEE ALSO"
1439.BR cat (1),
1440.BR find (1),
1441.BR free (1),
1442.BR mount (1),
1443.BR ps (1),
1444.BR tr (1),
1445.BR uptime (1),
1446.BR chroot (2),
1447.BR mmap (2),
1448.BR readlink (2),
1449.BR syslog (2),
1450.BR slabinfo (5),
1451.BR hier (7),
1452.BR arp (8),
1453.BR dmesg (8),
1454.BR hdparm (8),
1455.BR ifconfig (8),
1456.BR init (8),
1457.BR lsmod (8),
1458.BR lspci (8),
1459.BR netstat (8),
1460.BR procinfo (8),
1461.BR route (8)
1462.br
1463.I /usr/src/linux/Documentation/filesystems/proc.txt
1464.SH CAVEATS
1465Note that many strings (i.e., the environment and command line) are in
1466the internal format, with sub-fields terminated by NUL bytes, so you
1467may find that things are more readable if you use \fIod -c\fP or \fItr
1468"\\000" "\\n"\fP to read them.
1469Alternatively, \fIecho `cat <file>`\fP works well.
1470
1471This manual page is incomplete, possibly inaccurate, and is the kind
1472of thing that needs to be updated very often.
1473.SH ACKNOWLEDGEMENTS
1474The material on /proc/sys/fs and /proc/sys/kernel is closely based on
1475kernel source documentation files written by Rik van Riel.