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
61 /proc file system and we've used many freely available sources to write these
65 we know, it is the first 'all-in-one' document about the /proc file system. It
84 http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
104 * Investigating the properties of the pseudo file system /proc and its
106 * Examining /proc's structure
112 The proc file system acts as an interface to internal data structures in the
116 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
117 show you how you can use /proc/sys to change settings.
122 The directory /proc contains (among other things) one subdirectory for each
129 Table 1-1: Process specific entries in /proc
156 read the file /proc/PID/status:
158 >cat /proc/self/status
202 the ps command. In fact, ps uses the proc file system to obtain its
204 file /proc/PID/status. It fields are described in table 1-2.
214 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
334 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
354 The /proc/PID/maps file containing the currently mapped memory regions and
404 The /proc/PID/smaps is an extension based on maps, showing the memory
431 mapping in /proc/PID/maps. The remaining lines show the size of the mapping
504 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent
516 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
521 > echo 1 > /proc/PID/clear_refs
524 > echo 2 > /proc/PID/clear_refs
527 > echo 3 > /proc/PID/clear_refs
530 > echo 4 > /proc/PID/clear_refs
534 > echo 5 > /proc/PID/clear_refs
536 Any other value written to /proc/PID/clear_refs will have no effect.
538 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
539 using /proc/kpageflags and number of times a page is mapped using
540 /proc/kpagecount. For detailed explanation, see
543 The /proc/pid/numa_maps is an extension based on maps, showing the memory
579 /proc and are listed in Table 1-5. Not all of these will be present in your
583 Table 1-5: Kernel info in /proc
616 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
634 they are used for by looking in the file /proc/interrupts:
636 > cat /proc/interrupts
655 > cat /proc/interrupts
684 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
685 /proc/interrupts to display every IRQ vector in use by the system, not
712 Of some interest is the introduction of the /proc/irq directory to 2.4.
719 > ls /proc/irq/
722 > ls /proc/irq/0/
728 > echo 1 > /proc/irq/10/smp_affinity
735 > cat /proc/irq/0/smp_affinity
741 > cat /proc/irq/0/smp_affinity_list
746 /proc/irq/[0-9]* directory.
761 There are three more important subdirectories in /proc: net, scsi, and sys.
774 > cat /proc/buddyinfo
793 > cat /proc/pagetypeinfo
840 > cat /proc/meminfo
988 > cat /proc/vmallocinfo
1019 > cat /proc/softirqs
1032 1.3 IDE devices in /proc/ide
1035 The subdirectory /proc/ide contains information about all IDE devices of which
1043 > cat /proc/ide/drivers
1052 Table 1-6: IDE controller info in /proc/ide/ide?
1084 # cat /proc/ide/ide0/hda/settings
1105 1.4 Networking info in /proc/net
1108 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1113 Table 1-8: IPv6 info in /proc/net
1128 Table 1-9: Network info in /proc/net
1162 > cat /proc/net/dev
1176 example, the bond0 device will have a directory called /proc/net/bond0/.
1185 named after the driver for this adapter in /proc/scsi. You'll also see a list
1186 of all recognized SCSI devices in /proc/scsi:
1188 >cat /proc/scsi/scsi
1204 > cat /proc/scsi/aic7xxx/0
1244 1.6 Parallel port info in /proc/parport
1247 The directory /proc/parport contains information about the parallel ports of
1254 Table 1-10: Files in /proc/parport
1267 1.7 TTY info in /proc/tty
1271 directory /proc/tty.You'll find entries for drivers and line disciplines in
1275 Table 1-11: Files in /proc/tty
1284 /proc/tty/drivers:
1286 > cat /proc/tty/drivers
1300 1.8 Miscellaneous kernel statistics in /proc/stat
1304 /proc/stat file. All of the numbers reported in this file are aggregates
1307 > cat /proc/stat
1335 3. The value of iowait field in /proc/stat will decrease in certain
1337 So, the iowait is not reliable by reading from /proc/stat.
1375 /proc/fs/ext4. Each mounted filesystem will have a directory in
1376 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1377 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1380 Table 1-12: Files in /proc/fs/ext4/<devname>
1386 2.0 /proc/consoles
1391 /dev/console, you may simply look into the file /proc/consoles:
1393 > cat /proc/consoles
1414 The /proc file system serves information about the running system. It not only
1418 The directory structure of /proc reflects the types of information and makes
1429 * Modifying kernel parameters by writing into files found in /proc/sys
1431 * Review of the /proc/sys file tree
1435 A very interesting part of /proc is the directory /proc/sys. This is not only
1448 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1452 very careful when writing to any of these files. The entries in /proc may
1466 /proc/sys tree can not only be read, but also modified. You can use the echo
1475 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1500 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1509 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1516 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1520 scaled linearly with /proc/<pid>/oom_score_adj.
1522 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1532 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1536 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1540 3.3 /proc/<pid>/io - Display the IO accounting fields
1551 test:/tmp # cat /proc/3828/io
1635 process A reads process B's /proc/pid/io while process B is updating one of
1642 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1650 /proc/<pid>/coredump_filter allows you to customize which memory segments
1677 write 0x31 to the process's proc file.
1679 $ echo 0x31 > /proc/1234/coredump_filter
1685 $ echo 0x7 > /proc/self/coredump_filter
1688 3.5 /proc/<pid>/mountinfo - Information about mounts
1726 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1735 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1742 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1752 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1759 the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo
1873 3.9 /proc/<pid>/map_files - Information about memory mapped files
1889 files in a fast way instead of parsing /proc/<pid>/maps or
1890 /proc/<pid>/smaps, both of which contain many more records. At the same
1895 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
1911 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
1938 hidepid= Set /proc/<pid>/ access mode.
1941 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
1944 hidepid=1 means users may not access any /proc/<pid>/ directories but their
1948 As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
1952 hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be fully invisible to other
1956 /proc/<pid>/ otherwise. It greatly complicates an intruder's task of gathering