Lines Matching full:proc
4 The /proc Filesystem
8 /proc/sys Terrehon Bowden <terrehon@pacbell.net>, October 7 1999
11 move /proc/sys Shen Feng <shen@cn.fujitsu.com> April 1 2009
26 1.3 IDE devices in /proc/ide
27 1.4 Networking info in /proc/net
29 1.6 Parallel port info in /proc/parport
30 1.7 TTY info in /proc/tty
31 1.8 Miscellaneous kernel statistics in /proc/stat
37 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
39 3.2 /proc/<pid>/oom_score - Display current oom-killer score
40 3.3 /proc/<pid>/io - Display the IO accounting fields
41 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
42 3.5 /proc/<pid>/mountinfo - Information about mounts
43 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
44 3.7 /proc/<pid>/task/<tid>/children - Information about task children
45 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
46 3.9 /proc/<pid>/map_files - Information about memory mapped files
47 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
48 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
49 3.12 /proc/<pid>/arch_status - Task architecture specific information
64 /proc file system and we've used many freely available sources to write these
68 we know, it is the first 'all-in-one' document about the /proc file system. It
87 http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
105 * Investigating the properties of the pseudo file system /proc and its
107 * Examining /proc's structure
113 The proc file system acts as an interface to internal data structures in the
117 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
118 show you how you can use /proc/sys to change settings.
123 The directory /proc contains (among other things) one subdirectory for each
129 Note that an open file descriptor to /proc/<pid> or to any of its
132 open /proc/<pid> file descriptors corresponding to dead processes
137 .. table:: Table 1-1: Process specific entries in /proc
168 read the file /proc/PID/status::
170 >cat /proc/self/status
217 the ps command. In fact, ps uses the proc file system to obtain its
219 file /proc/PID/status. It fields are described in table 1-2.
230 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
363 use /proc/PID/wchan instead)
384 The /proc/PID/maps file contains the currently mapped memory regions and
436 The /proc/PID/smaps is an extension based on maps, showing the memory
467 mapping in /proc/PID/maps. Following lines show the size of the mapping
560 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent
572 The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps,
586 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
592 > echo 1 > /proc/PID/clear_refs
596 > echo 2 > /proc/PID/clear_refs
600 > echo 3 > /proc/PID/clear_refs
604 > echo 4 > /proc/PID/clear_refs
609 > echo 5 > /proc/PID/clear_refs
611 Any other value written to /proc/PID/clear_refs will have no effect.
613 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
614 using /proc/kpageflags and number of times a page is mapped using
615 /proc/kpagecount. For detailed explanation, see
618 The /proc/pid/numa_maps is an extension based on maps, showing the memory
657 /proc and are listed in Table 1-5. Not all of these will be present in your
661 .. table:: Table 1-5: Kernel info in /proc
696 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
714 they are used for by looking in the file /proc/interrupts::
716 > cat /proc/interrupts
735 > cat /proc/interrupts
764 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
765 /proc/interrupts to display every IRQ vector in use by the system, not
796 Of some interest is the introduction of the /proc/irq directory to 2.4.
804 > ls /proc/irq/
807 > ls /proc/irq/0/
813 > echo 1 > /proc/irq/10/smp_affinity
820 > cat /proc/irq/0/smp_affinity
826 > cat /proc/irq/0/smp_affinity_list
831 /proc/irq/[0-9]* directory.
846 There are three more important subdirectories in /proc: net, scsi, and sys.
859 > cat /proc/buddyinfo
878 > cat /proc/pagetypeinfo
927 > cat /proc/meminfo
1118 > cat /proc/vmallocinfo
1151 > cat /proc/softirqs
1164 1.3 IDE devices in /proc/ide
1167 The subdirectory /proc/ide contains information about all IDE devices of which
1175 > cat /proc/ide/drivers
1184 .. table:: Table 1-6: IDE controller info in /proc/ide/ide?
1220 # cat /proc/ide/ide0/hda/settings
1241 1.4 Networking info in /proc/net
1244 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1249 .. table:: Table 1-8: IPv6 info in /proc/net
1265 .. table:: Table 1-9: Network info in /proc/net
1301 > cat /proc/net/dev
1315 example, the bond0 device will have a directory called /proc/net/bond0/.
1324 named after the driver for this adapter in /proc/scsi. You'll also see a list
1325 of all recognized SCSI devices in /proc/scsi::
1327 >cat /proc/scsi/scsi
1343 > cat /proc/scsi/aic7xxx/0
1383 1.6 Parallel port info in /proc/parport
1386 The directory /proc/parport contains information about the parallel ports of
1393 .. table:: Table 1-10: Files in /proc/parport
1408 1.7 TTY info in /proc/tty
1412 directory /proc/tty. You'll find entries for drivers and line disciplines in
1416 .. table:: Table 1-11: Files in /proc/tty
1427 /proc/tty/drivers::
1429 > cat /proc/tty/drivers
1443 1.8 Miscellaneous kernel statistics in /proc/stat
1447 /proc/stat file. All of the numbers reported in this file are aggregates
1450 > cat /proc/stat
1479 3. The value of iowait field in /proc/stat will decrease in certain
1482 So, the iowait is not reliable by reading from /proc/stat.
1520 /proc/fs/ext4. Each mounted filesystem will have a directory in
1521 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1522 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1525 .. table:: Table 1-12: Files in /proc/fs/ext4/<devname>
1532 1.10 /proc/consoles
1537 /dev/console, you may simply look into the file /proc/consoles::
1539 > cat /proc/consoles
1566 The /proc file system serves information about the running system. It not only
1570 The directory structure of /proc reflects the types of information and makes
1579 * Modifying kernel parameters by writing into files found in /proc/sys
1581 * Review of the /proc/sys file tree
1585 A very interesting part of /proc is the directory /proc/sys. This is not only
1597 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1601 very careful when writing to any of these files. The entries in /proc may
1615 /proc/sys tree can not only be read, but also modified. You can use the echo
1623 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1645 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1654 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1661 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1665 scaled linearly with /proc/<pid>/oom_score_adj.
1667 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1672 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1676 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1683 3.3 /proc/<pid>/io - Display the IO accounting fields
1696 test:/tmp # cat /proc/3828/io
1779 if process A reads process B's /proc/pid/io while process B is updating one
1786 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1794 /proc/<pid>/coredump_filter allows you to customize which memory segments
1822 write 0x31 to the process's proc file::
1824 $ echo 0x31 > /proc/1234/coredump_filter
1830 $ echo 0x7 > /proc/self/coredump_filter
1833 3.5 /proc/<pid>/mountinfo - Information about mounts
1873 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1882 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1889 not be listed here; one needs to read /proc/<children-pid>/task/<tid>/children
1899 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1906 the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo
2031 3.9 /proc/<pid>/map_files - Information about memory mapped files
2047 files in a fast way instead of parsing /proc/<pid>/maps or
2048 /proc/<pid>/smaps, both of which contain many more records. At the same
2053 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
2069 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
2086 3.12 /proc/<pid>/arch_status - task architecture specific status
2096 $ cat /proc/6753/arch_status
2140 hidepid= Set /proc/<pid>/ access mode.
2146 /proc/<pid>/ directories (default).
2148 hidepid=noaccess or hidepid=1 means users may not access any /proc/<pid>/
2152 behaviour). As an additional bonus, as /proc/<pid>/cmdline is unaccessible for
2156 hidepid=invisible or hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be
2160 stat()'ing /proc/<pid>/ otherwise. It greatly complicates an intruder's task of
2166 /proc/<pid>/ directories that the caller can ptrace.
2185 # grep ^proc /proc/mounts
2186 proc /proc proc rw,relatime,hidepid=2 0 0
2188 # strace -e mount mount -o hidepid=1 -t proc proc /tmp/proc
2189 mount("proc", "/tmp/proc", "proc", 0, "hidepid=1") = 0
2192 # grep ^proc /proc/mounts
2193 proc /proc proc rw,relatime,hidepid=2 0 0
2194 proc /tmp/proc proc rw,relatime,hidepid=2 0 0
2199 # mount -o remount,hidepid=1 -t proc proc /tmp/proc
2201 # grep ^proc /proc/mounts
2202 proc /proc proc rw,relatime,hidepid=1 0 0
2203 proc /tmp/proc proc rw,relatime,hidepid=1 0 0
2212 # mount -o hidepid=invisible -t proc proc /proc
2213 # mount -o hidepid=noaccess -t proc proc /tmp/proc
2214 # grep ^proc /proc/mounts
2215 proc /proc proc rw,relatime,hidepid=invisible 0 0
2216 proc /tmp/proc proc rw,relatime,hidepid=noaccess 0 0