Lines Matching refs:proc
2 T H E /proc F I L E S Y S T E M
4 /proc/sys Terrehon Bowden <terrehon@pacbell.net> October 7 1999
8 move /proc/sys Shen Feng <shen@cn.fujitsu.com> April 1 2009
25 1.3 IDE devices in /proc/ide
26 1.4 Networking info in /proc/net
28 1.6 Parallel port info in /proc/parport
29 1.7 TTY info in /proc/tty
30 1.8 Miscellaneous kernel statistics in /proc/stat
36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
38 3.2 /proc/<pid>/oom_score - Display current oom-killer score
39 3.3 /proc/<pid>/io - Display the IO accounting fields
40 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
41 3.5 /proc/<pid>/mountinfo - Information about mounts
42 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
43 3.7 /proc/<pid>/task/<tid>/children - Information about task children
44 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
45 3.9 /proc/<pid>/map_files - Information about memory mapped files
46 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
47 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
48 3.12 /proc/<pid>/arch_status - Task architecture specific information
62 /proc file system and we've used many freely available sources to write these
66 we know, it is the first 'all-in-one' document about the /proc file system. It
85 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 a file descriptor to /proc/<pid> or to any of its
132 open /proc/<pid> file descriptors corresponding to dead processes
137 Table 1-1: Process specific entries in /proc
166 read the file /proc/PID/status:
168 >cat /proc/self/status
215 the ps command. In fact, ps uses the proc file system to obtain its
217 file /proc/PID/status. It fields are described in table 1-2.
227 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
351 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
371 The /proc/PID/maps file contains the currently mapped memory regions and
421 The /proc/PID/smaps is an extension based on maps, showing the memory
452 mapping in /proc/PID/maps. Following lines show the size of the mapping
532 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent
543 The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps,
557 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
562 > echo 1 > /proc/PID/clear_refs
565 > echo 2 > /proc/PID/clear_refs
568 > echo 3 > /proc/PID/clear_refs
571 > echo 4 > /proc/PID/clear_refs
575 > echo 5 > /proc/PID/clear_refs
577 Any other value written to /proc/PID/clear_refs will have no effect.
579 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
580 using /proc/kpageflags and number of times a page is mapped using
581 /proc/kpagecount. For detailed explanation, see
584 The /proc/pid/numa_maps is an extension based on maps, showing the memory
620 /proc and are listed in Table 1-5. Not all of these will be present in your
624 Table 1-5: Kernel info in /proc
657 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
675 they are used for by looking in the file /proc/interrupts:
677 > cat /proc/interrupts
696 > cat /proc/interrupts
725 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
726 /proc/interrupts to display every IRQ vector in use by the system, not
753 Of some interest is the introduction of the /proc/irq directory to 2.4.
760 > ls /proc/irq/
763 > ls /proc/irq/0/
769 > echo 1 > /proc/irq/10/smp_affinity
776 > cat /proc/irq/0/smp_affinity
782 > cat /proc/irq/0/smp_affinity_list
787 /proc/irq/[0-9]* directory.
802 There are three more important subdirectories in /proc: net, scsi, and sys.
815 > cat /proc/buddyinfo
834 > cat /proc/pagetypeinfo
881 > cat /proc/meminfo
1033 > cat /proc/vmallocinfo
1064 > cat /proc/softirqs
1077 1.3 IDE devices in /proc/ide
1080 The subdirectory /proc/ide contains information about all IDE devices of which
1088 > cat /proc/ide/drivers
1097 Table 1-6: IDE controller info in /proc/ide/ide?
1129 # cat /proc/ide/ide0/hda/settings
1150 1.4 Networking info in /proc/net
1153 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1158 Table 1-8: IPv6 info in /proc/net
1173 Table 1-9: Network info in /proc/net
1207 > cat /proc/net/dev
1221 example, the bond0 device will have a directory called /proc/net/bond0/.
1230 named after the driver for this adapter in /proc/scsi. You'll also see a list
1231 of all recognized SCSI devices in /proc/scsi:
1233 >cat /proc/scsi/scsi
1249 > cat /proc/scsi/aic7xxx/0
1289 1.6 Parallel port info in /proc/parport
1292 The directory /proc/parport contains information about the parallel ports of
1299 Table 1-10: Files in /proc/parport
1312 1.7 TTY info in /proc/tty
1316 directory /proc/tty.You'll find entries for drivers and line disciplines in
1320 Table 1-11: Files in /proc/tty
1329 /proc/tty/drivers:
1331 > cat /proc/tty/drivers
1345 1.8 Miscellaneous kernel statistics in /proc/stat
1349 /proc/stat file. All of the numbers reported in this file are aggregates
1352 > cat /proc/stat
1380 3. The value of iowait field in /proc/stat will decrease in certain
1382 So, the iowait is not reliable by reading from /proc/stat.
1420 /proc/fs/ext4. Each mounted filesystem will have a directory in
1421 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1422 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1425 Table 1-12: Files in /proc/fs/ext4/<devname>
1431 2.0 /proc/consoles
1436 /dev/console, you may simply look into the file /proc/consoles:
1438 > cat /proc/consoles
1459 The /proc file system serves information about the running system. It not only
1463 The directory structure of /proc reflects the types of information and makes
1474 * Modifying kernel parameters by writing into files found in /proc/sys
1476 * Review of the /proc/sys file tree
1480 A very interesting part of /proc is the directory /proc/sys. This is not only
1493 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1497 very careful when writing to any of these files. The entries in /proc may
1511 /proc/sys tree can not only be read, but also modified. You can use the echo
1520 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1545 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1554 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1561 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1565 scaled linearly with /proc/<pid>/oom_score_adj.
1567 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1577 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1581 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1585 3.3 /proc/<pid>/io - Display the IO accounting fields
1596 test:/tmp # cat /proc/3828/io
1680 process A reads process B's /proc/pid/io while process B is updating one of
1687 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1695 /proc/<pid>/coredump_filter allows you to customize which memory segments
1722 write 0x31 to the process's proc file.
1724 $ echo 0x31 > /proc/1234/coredump_filter
1730 $ echo 0x7 > /proc/self/coredump_filter
1733 3.5 /proc/<pid>/mountinfo - Information about mounts
1771 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1780 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1787 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1797 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1804 the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo
1918 3.9 /proc/<pid>/map_files - Information about memory mapped files
1934 files in a fast way instead of parsing /proc/<pid>/maps or
1935 /proc/<pid>/smaps, both of which contain many more records. At the same
1940 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
1956 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
1973 3.12 /proc/<pid>/arch_status - task architecture specific status
1980 $ cat /proc/6753/arch_status
2022 hidepid= Set /proc/<pid>/ access mode.
2025 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
2028 hidepid=1 means users may not access any /proc/<pid>/ directories but their
2032 As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
2036 hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be fully invisible to other
2040 /proc/<pid>/ otherwise. It greatly complicates an intruder's task of gathering