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
59 /proc file system and we've used many freely available sources to write these
63 we know, it is the first 'all-in-one' document about the /proc file system. It
82 http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
102 * Investigating the properties of the pseudo file system /proc and its
104 * Examining /proc's structure
110 The proc file system acts as an interface to internal data structures in the
114 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
115 show you how you can use /proc/sys to change settings.
120 The directory /proc contains (among other things) one subdirectory for each
127 Table 1-1: Process specific entries in /proc
154 read the file /proc/PID/status:
156 >cat /proc/self/status
194 the ps command. In fact, ps uses the proc file system to obtain its
196 file /proc/PID/status. It fields are described in table 1-2.
206 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
313 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
333 The /proc/PID/maps file containing the currently mapped memory regions and
384 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
387 content of /proc/PID/maps, where you will see all mappings that are being used
389 map, i.e. /proc/PID/task/TID/maps for thread 1001 will look like this:
412 The /proc/PID/smaps is an extension based on maps, showing the memory
433 mapping in /proc/PID/maps. The remaining lines show the size of the mapping
485 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
489 > echo 1 > /proc/PID/clear_refs
492 > echo 2 > /proc/PID/clear_refs
495 > echo 3 > /proc/PID/clear_refs
498 > echo 4 > /proc/PID/clear_refs
502 > echo 5 > /proc/PID/clear_refs
504 Any other value written to /proc/PID/clear_refs will have no effect.
506 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
507 using /proc/kpageflags and number of times a page is mapped using
508 /proc/kpagecount. For detailed explanation, see Documentation/vm/pagemap.txt.
510 The /proc/pid/numa_maps is an extension based on maps, showing the memory
546 /proc and are listed in Table 1-5. Not all of these will be present in your
550 Table 1-5: Kernel info in /proc
583 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
601 they are used for by looking in the file /proc/interrupts:
603 > cat /proc/interrupts
622 > cat /proc/interrupts
651 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
652 /proc/interrupts to display every IRQ vector in use by the system, not
679 Of some interest is the introduction of the /proc/irq directory to 2.4.
686 > ls /proc/irq/
689 > ls /proc/irq/0/
695 > echo 1 > /proc/irq/10/smp_affinity
702 > cat /proc/irq/0/smp_affinity
708 > cat /proc/irq/0/smp_affinity_list
713 /proc/irq/[0-9]* directory.
728 There are three more important subdirectories in /proc: net, scsi, and sys.
741 > cat /proc/buddyinfo
760 > cat /proc/pagetypeinfo
807 > cat /proc/meminfo
944 > cat /proc/vmallocinfo
975 > cat /proc/softirqs
988 1.3 IDE devices in /proc/ide
991 The subdirectory /proc/ide contains information about all IDE devices of which
999 > cat /proc/ide/drivers
1008 Table 1-6: IDE controller info in /proc/ide/ide?
1040 # cat /proc/ide/ide0/hda/settings
1061 1.4 Networking info in /proc/net
1064 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1069 Table 1-8: IPv6 info in /proc/net
1084 Table 1-9: Network info in /proc/net
1118 > cat /proc/net/dev
1132 example, the bond0 device will have a directory called /proc/net/bond0/.
1141 named after the driver for this adapter in /proc/scsi. You'll also see a list
1142 of all recognized SCSI devices in /proc/scsi:
1144 >cat /proc/scsi/scsi
1160 > cat /proc/scsi/aic7xxx/0
1200 1.6 Parallel port info in /proc/parport
1203 The directory /proc/parport contains information about the parallel ports of
1210 Table 1-10: Files in /proc/parport
1223 1.7 TTY info in /proc/tty
1227 directory /proc/tty.You'll find entries for drivers and line disciplines in
1231 Table 1-11: Files in /proc/tty
1240 /proc/tty/drivers:
1242 > cat /proc/tty/drivers
1256 1.8 Miscellaneous kernel statistics in /proc/stat
1260 /proc/stat file. All of the numbers reported in this file are aggregates
1263 > cat /proc/stat
1322 /proc/fs/ext4. Each mounted filesystem will have a directory in
1323 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1324 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1327 Table 1-12: Files in /proc/fs/ext4/<devname>
1333 2.0 /proc/consoles
1338 /dev/console, you may simply look into the file /proc/consoles:
1340 > cat /proc/consoles
1361 The /proc file system serves information about the running system. It not only
1365 The directory structure of /proc reflects the types of information and makes
1376 * Modifying kernel parameters by writing into files found in /proc/sys
1378 * Review of the /proc/sys file tree
1382 A very interesting part of /proc is the directory /proc/sys. This is not only
1395 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1399 very careful when writing to any of these files. The entries in /proc may
1413 /proc/sys tree can not only be read, but also modified. You can use the echo
1422 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1447 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1456 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1463 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1467 scaled linearly with /proc/<pid>/oom_score_adj.
1469 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1479 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1483 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1487 3.3 /proc/<pid>/io - Display the IO accounting fields
1498 test:/tmp # cat /proc/3828/io
1582 process A reads process B's /proc/pid/io while process B is updating one of
1589 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1597 /proc/<pid>/coredump_filter allows you to customize which memory segments
1622 write 0x21 to the process's proc file.
1624 $ echo 0x21 > /proc/1234/coredump_filter
1630 $ echo 0x7 > /proc/self/coredump_filter
1633 3.5 /proc/<pid>/mountinfo - Information about mounts
1671 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1680 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1687 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1697 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1704 the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo
1814 3.9 /proc/<pid>/map_files - Information about memory mapped files
1830 files in a fast way instead of parsing /proc/<pid>/maps or
1831 /proc/<pid>/smaps, both of which contain many more records. At the same
1845 hidepid= Set /proc/<pid>/ access mode.
1848 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
1851 hidepid=1 means users may not access any /proc/<pid>/ directories but their
1855 As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
1859 hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be fully invisible to other
1863 /proc/<pid>/ otherwise. It greatly complicates an intruder's task of gathering