Lines Matching full:pid
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
124 process running on the system, which is named after the process ID (PID).
129 Note that an open a file descriptor to /proc/<pid> or to any of its
130 contained files or subdirectories does not prevent <pid> being reused
131 for some other process in the event that <pid> exits. Operations on
132 open /proc/<pid> file descriptors corresponding to dead processes
134 also assigned the process ID <pid>. Instead, operations on these FDs
166 read the file /proc/PID/status:
172 Pid: 5452
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.
240 Pid process id
242 TracerPid PID of process tracing this process (0 if not)
316 pid process id
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
423 The /proc/PID/smaps is an extension based on maps, showing the memory
455 mapping in /proc/PID/maps. Following lines show the size of the mapping
538 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent
549 The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps,
563 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
568 > echo 1 > /proc/PID/clear_refs
571 > echo 2 > /proc/PID/clear_refs
574 > echo 3 > /proc/PID/clear_refs
577 > echo 4 > /proc/PID/clear_refs
581 > echo 5 > /proc/PID/clear_refs
583 Any other value written to /proc/PID/clear_refs will have no effect.
585 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
590 The /proc/pid/numa_maps is an extension based on maps, showing the memory
1526 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1551 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1560 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1567 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1571 scaled linearly with /proc/<pid>/oom_score_adj.
1573 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1583 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1587 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1591 3.3 /proc/<pid>/io - Display the IO accounting fields
1686 process A reads process B's /proc/pid/io while process B is updating one of
1693 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1701 /proc/<pid>/coredump_filter allows you to customize which memory segments
1702 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
1727 If you don't want to dump all shared memory segments attached to pid 1234,
1739 3.5 /proc/<pid>/mountinfo - Information about mounts
1777 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1786 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1789 of a task pointed by <pid>/<tid> pair. The format is a space separated
1793 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1803 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1810 the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo
1924 3.9 /proc/<pid>/map_files - Information about memory mapped files
1940 files in a fast way instead of parsing /proc/<pid>/maps or
1941 /proc/<pid>/smaps, both of which contain many more records. At the same
1946 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
1962 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
1979 3.12 /proc/<pid>/arch_status - task architecture specific status
2028 hidepid= Set /proc/<pid>/ access mode.
2031 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
2034 hidepid=1 means users may not access any /proc/<pid>/ directories but their
2038 As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
2042 hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be fully invisible to other
2044 pid value exists (it can be learned by other means, e.g. by "kill -0 $PID"),
2046 /proc/<pid>/ otherwise. It greatly complicates an intruder's task of gathering