|
 |
d4f532 |
[](https://gitlab.com/ci/projects/2142?ref=master)
|
|
|
d4f532 |
procps
|
|
|
d4f532 |
======
|
|
|
d4f532 |
|
|
|
d4f532 |
procps is a set of command line and full-screen utilities that provide
|
|
|
d4f532 |
information out of the pseudo-filesystem most commonly located at /proc.
|
|
|
d4f532 |
This filesystem provides a simple interface to the kernel data structures.
|
|
|
d4f532 |
The programs of procps generally concentrate on the structures that describe
|
|
|
d4f532 |
the processess running on the system.
|
|
|
d4f532 |
|
|
|
d4f532 |
The following programs are found in procps:
|
|
|
d4f532 |
* *free* - Report the amount of free and used memory in the system
|
|
|
d4f532 |
* *kill* - Send a signal to a process based on PID
|
|
|
d4f532 |
* *pgrep* - List processes based on name or other attributes
|
|
|
d4f532 |
* *pkill* - Send a signal to a process based on name or other attributes
|
|
|
d4f532 |
* *pmap* - Report memory map of a process
|
|
|
d4f532 |
* *ps* - Report information of processes
|
|
|
d4f532 |
* *pwdx* - Report current directory of a process
|
|
|
d4f532 |
* *skill* - Obsolete version of pgrep/pkill
|
|
|
d4f532 |
* *slabtop* - Display kernel slab cache information in real time
|
|
|
d4f532 |
* *snice* - Renice a process
|
|
|
d4f532 |
* *sysctl* - Read or Write kernel parameters at run-time
|
|
|
d4f532 |
* *tload* - Graphical representation of system load average
|
|
|
d4f532 |
* *top* - Dynamic real-time view of running processes
|
|
|
d4f532 |
* *uptime* - Display how long the system has been running
|
|
|
d4f532 |
* *vmstat* - Report virtual memory statistics
|
|
|
d4f532 |
* *w* - Report logged in users and what they are doing
|
|
|
d4f532 |
* *watch* - Execute a program periodically, showing output fullscreen
|
|
|
d4f532 |
|
|
|
d4f532 |
## Reporting Bugs
|
|
|
d4f532 |
There are a few ways of reporting bugs or feature requests:
|
|
|
d4f532 |
|
|
|
d4f532 |
1. Your distributions bug reporter. If you are using a distribution your first
|
|
|
d4f532 |
port of call is their bug tracker. This is because each distribution has their
|
|
|
d4f532 |
own patches and way of dealing with bugs. Also bug reporting often does not need
|
|
|
d4f532 |
any subscription to websites.
|
|
|
d4f532 |
2. GitLab Issues - To the left of this page is the issue tracker. You can report
|
|
|
d4f532 |
bugs here.
|
|
|
d4f532 |
3. Email list - We have an email list (see below) where you can report bugs.
|
|
|
d4f532 |
The problem with this method is bug reports often get lost and cannot be
|
|
|
d4f532 |
tracked. This is especially a big problem when its something that will take
|
|
|
d4f532 |
time to resolve.
|
|
|
d4f532 |
|
|
|
d4f532 |
If you need to report bugs, there is more details on the
|
|
|
d4f532 |
[Bug Reporting](https://gitlab.com/procps-ng/procps/blob/master/Documentation/bugs.md)
|
|
|
d4f532 |
page.
|
|
|
d4f532 |
|
|
|
d4f532 |
## Email List
|
|
|
d4f532 |
The email list for the developers and users of procps is found at
|
|
|
d4f532 |
http://www.freelists.org/archive/procps/
|
|
|
d4f532 |
This email list discusses the development of procps and is used by distributions
|
|
|
d4f532 |
to also forward or discuss bugs.
|