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
50 3.13 /proc/<pid>/fd - List of symlinks to open files
65 /proc file system and we've used many freely available sources to write these
69 we know, it is the first 'all-in-one' document about the /proc file system. It
88 https://www.kernel.org/doc/html/latest/filesystems/proc.html
106 * Investigating the properties of the pseudo file system /proc and its
108 * Examining /proc's structure
114 The proc file system acts as an interface to internal data structures in the
118 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
119 show you how you can use /proc/sys to change settings.
124 The directory /proc contains (among other things) one subdirectory for each
130 Note that an open file descriptor to /proc/<pid> or to any of its
133 open /proc/<pid> file descriptors corresponding to dead processes
138 .. table:: Table 1-1: Process specific entries in /proc
169 read the file /proc/PID/status::
171 >cat /proc/self/status
220 the ps command. In fact, ps uses the proc file system to obtain its
222 file /proc/PID/status. It fields are described in table 1-2.
233 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
369 use /proc/PID/wchan instead)
390 The /proc/PID/maps file contains the currently mapped memory regions and
446 The /proc/PID/smaps is an extension based on maps, showing the memory
479 mapping in /proc/PID/maps. Following lines show the size of the mapping
585 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent
597 The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps,
611 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
617 > echo 1 > /proc/PID/clear_refs
621 > echo 2 > /proc/PID/clear_refs
625 > echo 3 > /proc/PID/clear_refs
629 > echo 4 > /proc/PID/clear_refs
634 > echo 5 > /proc/PID/clear_refs
636 Any other value written to /proc/PID/clear_refs will have no effect.
638 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
639 using /proc/kpageflags and number of times a page is mapped using
640 /proc/kpagecount. For detailed explanation, see
643 The /proc/pid/numa_maps is an extension based on maps, showing the memory
682 /proc and are listed in Table 1-5. Not all of these will be present in your
686 .. table:: Table 1-5: Kernel info in /proc
728 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
746 they are used for by looking in the file /proc/interrupts::
748 > cat /proc/interrupts
767 > cat /proc/interrupts
796 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
797 /proc/interrupts to display every IRQ vector in use by the system, not
828 Of some interest is the introduction of the /proc/irq directory to 2.4.
836 > ls /proc/irq/
839 > ls /proc/irq/0/
845 > echo 1 > /proc/irq/10/smp_affinity
852 > cat /proc/irq/0/smp_affinity
858 > cat /proc/irq/0/smp_affinity_list
863 /proc/irq/[0-9]* directory.
878 There are three more important subdirectories in /proc: net, scsi, and sys.
891 > cat /proc/buddyinfo
910 > cat /proc/pagetypeinfo
959 /proc/net/sockstat for TCP memory allocations.
965 > cat /proc/meminfo
1211 > cat /proc/vmallocinfo
1244 > cat /proc/softirqs
1256 1.3 Networking info in /proc/net
1259 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1264 .. table:: Table 1-8: IPv6 info in /proc/net
1280 .. table:: Table 1-9: Network info in /proc/net
1317 > cat /proc/net/dev
1331 example, the bond0 device will have a directory called /proc/net/bond0/.
1340 subdirectory named after the driver for this adapter in /proc/scsi.
1341 You'll also see a list of all recognized SCSI devices in /proc/scsi::
1343 >cat /proc/scsi/scsi
1359 > cat /proc/scsi/aic7xxx/0
1399 1.5 Parallel port info in /proc/parport
1402 The directory /proc/parport contains information about the parallel ports of
1409 .. table:: Table 1-10: Files in /proc/parport
1424 1.6 TTY info in /proc/tty
1428 directory /proc/tty. You'll find entries for drivers and line disciplines in
1432 .. table:: Table 1-11: Files in /proc/tty
1443 /proc/tty/drivers::
1445 > cat /proc/tty/drivers
1459 1.7 Miscellaneous kernel statistics in /proc/stat
1463 /proc/stat file. All of the numbers reported in this file are aggregates
1466 > cat /proc/stat
1497 3. The value of iowait field in /proc/stat will decrease in certain
1500 So, the iowait is not reliable by reading from /proc/stat.
1538 /proc/fs/ext4. Each mounted filesystem will have a directory in
1539 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1540 /proc/fs/ext4/sda9 or /proc/fs/ext4/dm-0). The files in each per-device
1543 .. table:: Table 1-12: Files in /proc/fs/ext4/<devname>
1550 1.9 /proc/consoles
1555 /dev/console, you may simply look into the file /proc/consoles::
1557 > cat /proc/consoles
1584 The /proc file system serves information about the running system. It not only
1588 The directory structure of /proc reflects the types of information and makes
1597 * Modifying kernel parameters by writing into files found in /proc/sys
1599 * Review of the /proc/sys file tree
1603 A very interesting part of /proc is the directory /proc/sys. This is not only
1615 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1619 very careful when writing to any of these files. The entries in /proc may
1633 /proc/sys tree can not only be read, but also modified. You can use the echo
1641 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1663 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1672 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1679 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1683 scaled linearly with /proc/<pid>/oom_score_adj.
1685 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1690 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1694 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1701 3.3 /proc/<pid>/io - Display the IO accounting fields
1714 test:/tmp # cat /proc/3828/io
1797 if process A reads process B's /proc/pid/io while process B is updating one
1804 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1812 /proc/<pid>/coredump_filter allows you to customize which memory segments
1840 write 0x31 to the process's proc file::
1842 $ echo 0x31 > /proc/1234/coredump_filter
1848 $ echo 0x7 > /proc/self/coredump_filter
1851 3.5 /proc/<pid>/mountinfo - Information about mounts
1891 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1900 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1907 not be listed here; one needs to read /proc/<children-pid>/task/<tid>/children
1917 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1925 /proc/<pid>/mountinfo for details]. 'ino' represents the inode number of
2074 3.9 /proc/<pid>/map_files - Information about memory mapped files
2090 files in a fast way instead of parsing /proc/<pid>/maps or
2091 /proc/<pid>/smaps, both of which contain many more records. At the same
2096 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
2112 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
2129 3.12 /proc/<pid>/arch_status - task architecture specific status
2139 $ cat /proc/6753/arch_status
2174 3.13 /proc/<pid>/fd - List of symlinks to open files
2186 of stat() output for /proc/<pid>/fd for fast access.
2199 hidepid= Set /proc/<pid>/ access mode.
2205 /proc/<pid>/ directories (default).
2207 hidepid=noaccess or hidepid=1 means users may not access any /proc/<pid>/
2211 behaviour). As an additional bonus, as /proc/<pid>/cmdline is unaccessible for
2215 hidepid=invisible or hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be
2219 stat()'ing /proc/<pid>/ otherwise. It greatly complicates an intruder's task of
2225 /proc/<pid>/ directories that the caller can ptrace.
2244 # grep ^proc /proc/mounts
2245 proc /proc proc rw,relatime,hidepid=2 0 0
2247 # strace -e mount mount -o hidepid=1 -t proc proc /tmp/proc
2248 mount("proc", "/tmp/proc", "proc", 0, "hidepid=1") = 0
2251 # grep ^proc /proc/mounts
2252 proc /proc proc rw,relatime,hidepid=2 0 0
2253 proc /tmp/proc proc rw,relatime,hidepid=2 0 0
2258 # mount -o remount,hidepid=1 -t proc proc /tmp/proc
2260 # grep ^proc /proc/mounts
2261 proc /proc proc rw,relatime,hidepid=1 0 0
2262 proc /tmp/proc proc rw,relatime,hidepid=1 0 0
2271 # mount -o hidepid=invisible -t proc proc /proc
2272 # mount -o hidepid=noaccess -t proc proc /tmp/proc
2273 # grep ^proc /proc/mounts
2274 proc /proc proc rw,relatime,hidepid=invisible 0 0
2275 proc /tmp/proc proc rw,relatime,hidepid=noaccess 0 0