Lines Matching full:proc
4 The /proc Filesystem
8 /proc/sys Terrehon Bowden <[email protected]>, October 7 1999
11 move /proc/sys Shen Feng <[email protected]> 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
51 3.14 /proc/<pid/ksm_stat - Information about the process's ksm status.
66 /proc file system and we've used many freely available sources to write these
70 we know, it is the first 'all-in-one' document about the /proc file system. It
89 https://www.kernel.org/doc/html/latest/filesystems/proc.html
107 * Investigating the properties of the pseudo file system /proc and its
109 * Examining /proc's structure
115 The proc file system acts as an interface to internal data structures in the
119 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
120 show you how you can use /proc/sys to change settings.
125 The directory /proc contains (among other things) one subdirectory for each
131 Note that an open file descriptor to /proc/<pid> or to any of its
134 open /proc/<pid> file descriptors corresponding to dead processes
139 .. table:: Table 1-1: Process specific entries in /proc
170 read the file /proc/PID/status::
172 >cat /proc/self/status
221 the ps command. In fact, ps uses the proc file system to obtain its
223 file /proc/PID/status. It fields are described in table 1-2.
234 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
370 use /proc/PID/wchan instead)
391 The /proc/PID/maps file contains the currently mapped memory regions and
447 Starting with 6.11 kernel, /proc/PID/maps provides an alternative
456 The /proc/PID/smaps is an extension based on maps, showing the memory
489 the mapping in /proc/PID/maps. Following lines show the size of the
597 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent
609 The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps,
623 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
629 > echo 1 > /proc/PID/clear_refs
633 > echo 2 > /proc/PID/clear_refs
637 > echo 3 > /proc/PID/clear_refs
641 > echo 4 > /proc/PID/clear_refs
646 > echo 5 > /proc/PID/clear_refs
648 Any other value written to /proc/PID/clear_refs will have no effect.
650 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
651 using /proc/kpageflags and number of times a page is mapped using
652 /proc/kpagecount. For detailed explanation, see
655 The /proc/pid/numa_maps is an extension based on maps, showing the memory
694 /proc and are listed in Table 1-5. Not all of these will be present in your
698 .. table:: Table 1-5: Kernel info in /proc
747 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
765 they are used for by looking in the file /proc/interrupts::
767 > cat /proc/interrupts
786 > cat /proc/interrupts
815 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
816 /proc/interrupts to display every IRQ vector in use by the system, not
847 Of some interest is the introduction of the /proc/irq directory to 2.4.
855 > ls /proc/irq/
858 > ls /proc/irq/0/
864 > echo 1 > /proc/irq/10/smp_affinity
871 > cat /proc/irq/0/smp_affinity
877 > cat /proc/irq/0/smp_affinity_list
882 /proc/irq/[0-9]* directory.
897 There are three more important subdirectories in /proc: net, scsi, and sys.
910 > cat /proc/buddyinfo
929 > cat /proc/pagetypeinfo
983 > tail -n +3 /proc/allocinfo | sort -rn
1007 /proc/net/sockstat for TCP memory allocations.
1013 > cat /proc/meminfo
1259 > cat /proc/vmallocinfo
1292 > cat /proc/softirqs
1304 1.3 Networking info in /proc/net
1307 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1312 .. table:: Table 1-8: IPv6 info in /proc/net
1328 .. table:: Table 1-9: Network info in /proc/net
1365 > cat /proc/net/dev
1379 example, the bond0 device will have a directory called /proc/net/bond0/.
1388 subdirectory named after the driver for this adapter in /proc/scsi.
1389 You'll also see a list of all recognized SCSI devices in /proc/scsi::
1391 >cat /proc/scsi/scsi
1407 > cat /proc/scsi/aic7xxx/0
1447 1.5 Parallel port info in /proc/parport
1450 The directory /proc/parport contains information about the parallel ports of
1457 .. table:: Table 1-10: Files in /proc/parport
1472 1.6 TTY info in /proc/tty
1476 directory /proc/tty. You'll find entries for drivers and line disciplines in
1480 .. table:: Table 1-11: Files in /proc/tty
1491 /proc/tty/drivers::
1493 > cat /proc/tty/drivers
1507 1.7 Miscellaneous kernel statistics in /proc/stat
1511 /proc/stat file. All of the numbers reported in this file are aggregates
1514 > cat /proc/stat
1545 3. The value of iowait field in /proc/stat will decrease in certain
1548 So, the iowait is not reliable by reading from /proc/stat.
1586 /proc/fs/ext4. Each mounted filesystem will have a directory in
1587 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1588 /proc/fs/ext4/sda9 or /proc/fs/ext4/dm-0). The files in each per-device
1591 .. table:: Table 1-12: Files in /proc/fs/ext4/<devname>
1598 1.9 /proc/consoles
1603 /dev/console, you may simply look into the file /proc/consoles::
1605 > cat /proc/consoles
1632 The /proc file system serves information about the running system. It not only
1636 The directory structure of /proc reflects the types of information and makes
1645 * Modifying kernel parameters by writing into files found in /proc/sys
1647 * Review of the /proc/sys file tree
1651 A very interesting part of /proc is the directory /proc/sys. This is not only
1663 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1667 very careful when writing to any of these files. The entries in /proc may
1681 /proc/sys tree can not only be read, but also modified. You can use the echo
1689 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1711 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1720 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1727 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1731 scaled linearly with /proc/<pid>/oom_score_adj.
1733 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1738 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1742 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1749 3.3 /proc/<pid>/io - Display the IO accounting fields
1762 test:/tmp # cat /proc/3828/io
1845 if process A reads process B's /proc/pid/io while process B is updating one
1852 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1860 /proc/<pid>/coredump_filter allows you to customize which memory segments
1888 write 0x31 to the process's proc file::
1890 $ echo 0x31 > /proc/1234/coredump_filter
1896 $ echo 0x7 > /proc/self/coredump_filter
1899 3.5 /proc/<pid>/mountinfo - Information about mounts
1939 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1948 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1955 not be listed here; one needs to read /proc/<children-pid>/task/<tid>/children
1965 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1973 /proc/<pid>/mountinfo for details]. 'ino' represents the inode number of
2122 3.9 /proc/<pid>/map_files - Information about memory mapped files
2138 files in a fast way instead of parsing /proc/<pid>/maps or
2139 /proc/<pid>/smaps, both of which contain many more records. At the same
2144 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
2160 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
2177 3.12 /proc/<pid>/arch_status - task architecture specific status
2187 $ cat /proc/6753/arch_status
2222 3.13 /proc/<pid>/fd - List of symlinks to open files
2234 of stat() output for /proc/<pid>/fd for fast access.
2237 3.14 /proc/<pid/ksm_stat - Information about the process's ksm status
2247 / # cat /proc/self/ksm_stat
2277 /proc/<pid>/ksm_merging_pages shows.
2315 hidepid= Set /proc/<pid>/ access mode.
2321 /proc/<pid>/ directories (default).
2323 hidepid=noaccess or hidepid=1 means users may not access any /proc/<pid>/
2327 behaviour). As an additional bonus, as /proc/<pid>/cmdline is unaccessible for
2331 hidepid=invisible or hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be
2335 stat()'ing /proc/<pid>/ otherwise. It greatly complicates an intruder's task of
2341 /proc/<pid>/ directories that the caller can ptrace.
2360 # grep ^proc /proc/mounts
2361 proc /proc proc rw,relatime,hidepid=2 0 0
2363 # strace -e mount mount -o hidepid=1 -t proc proc /tmp/proc
2364 mount("proc", "/tmp/proc", "proc", 0, "hidepid=1") = 0
2367 # grep ^proc /proc/mounts
2368 proc /proc proc rw,relatime,hidepid=2 0 0
2369 proc /tmp/proc proc rw,relatime,hidepid=2 0 0
2374 # mount -o remount,hidepid=1 -t proc proc /tmp/proc
2376 # grep ^proc /proc/mounts
2377 proc /proc proc rw,relatime,hidepid=1 0 0
2378 proc /tmp/proc proc rw,relatime,hidepid=1 0 0
2387 # mount -o hidepid=invisible -t proc proc /proc
2388 # mount -o hidepid=noaccess -t proc proc /tmp/proc
2389 # grep ^proc /proc/mounts
2390 proc /proc proc rw,relatime,hidepid=invisible 0 0
2391 proc /tmp/proc proc rw,relatime,hidepid=noaccess 0 0