Command line and full screen utilities for browsing procfs, a "pseudo" file system dynamically generated by Linux to provide information about the status of entries in its process table.
ed8dbd05e7
[ the original newlib commit message(s) appear below ] [ but 'cpu utilization' was not implemented to avoid ] [ any library modifications and thus version impact! ] --------------------------------- newlib patch #1 --- top: added fields for 'start time' & 'cpu utilization' This patch will exploit some new library capabilities. [ one will raise eyebrows, the other likely will not ] A new 'STARTED' field was added which shows the time a process started after system boot. As such the largest interval represents the most recently started process. This is the field that will likely be questioned since it's somewhat counterintuitive. But were we to instead use TIME_ELAPSED, the value will change with every top refresh. This will defeat any PUFF macro optimization. The new '%CUU' field will probably be better received. It represents the cpu usage over the life of the task. When a process was showing high %CPU usage, this field can be used to determine if it's an anomaly or normal. [ and as with %CPU, %CUU shows a '?' when running in ] [ a namespace when /proc was mounted with subset=pid ] ---------------------------------- newlib patch #2 --- top: tweaked the recently introduced 'STARTED' support When the 'STARTED' field was added, the width was made the same as the 'TIME+' field. Thus, a full time could be shown (which then included hundredths of a second). That kind of granularity is totally unnecessary. After all, this column is potentially confusing enough since it is so counterintuitive. So, this commit will reduce the width of the field with some help from scale_tics. Henceforth it will not include those ol' centiseconds. [ along the way let's expand the man document with a ] [ a remainder about content representation & scaling ] Signed-off-by: Jim Warner <james.warner@comcast.net> |
||
|---|---|---|
| contrib | ||
| Documentation | ||
| include | ||
| lib | ||
| man-po | ||
| misc | ||
| po | ||
| proc | ||
| ps | ||
| testsuite | ||
| top | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| COPYING.LIB | ||
| create-man-pot.sh | ||
| free.1 | ||
| free.c | ||
| INSTALL.md | ||
| kill.1 | ||
| Makefile.am | ||
| NEWS | ||
| pgrep.1 | ||
| pgrep.c | ||
| pidof.1 | ||
| pidof.c | ||
| pidwait.1 | ||
| pkill.1 | ||
| pmap.1 | ||
| pmap.c | ||
| procio.c | ||
| pwdx.1 | ||
| pwdx.c | ||
| README.md | ||
| skill.1 | ||
| skill.c | ||
| slabtop.1 | ||
| slabtop.c | ||
| snice.1 | ||
| sysctl.8 | ||
| sysctl.c | ||
| sysctl.conf | ||
| sysctl.conf.5 | ||
| tload.1 | ||
| tload.c | ||
| translate-man.sh | ||
| uptime.1 | ||
| uptime.c | ||
| vmstat.8 | ||
| vmstat.c | ||
| w.1 | ||
| w.c | ||
| watch.1 | ||
| watch.c | ||
procps
procps is a set of command line and full-screen utilities that provide information out of the pseudo-filesystem most commonly located at /proc. This filesystem provides a simple interface to the kernel data structures. The programs of procps generally concentrate on the structures that describe the processess running on the system.
The following programs are found in procps:
- free - Report the amount of free and used memory in the system
- kill - Send a signal to a process based on PID
- pgrep - List processes based on name or other attributes
- pkill - Send a signal to a process based on name or other attributes
- pmap - Report memory map of a process
- ps - Report information of processes
- pwdx - Report current directory of a process
- skill - Obsolete version of pgrep/pkill
- slabtop - Display kernel slab cache information in real time
- snice - Renice a process
- sysctl - Read or Write kernel parameters at run-time
- tload - Graphical representation of system load average
- top - Dynamic real-time view of running processes
- uptime - Display how long the system has been running
- vmstat - Report virtual memory statistics
- w - Report logged in users and what they are doing
- watch - Execute a program periodically, showing output fullscreen
Reporting Bugs
There are a few ways of reporting bugs or feature requests:
- Your distributions bug reporter. If you are using a distribution your first port of call is their bug tracker. This is because each distribution has their own patches and way of dealing with bugs. Also bug reporting often does not need any subscription to websites.
- GitLab Issues - To the left of this page is the issue tracker. You can report bugs here.
- Email list - We have an email list (see below) where you can report bugs. The problem with this method is bug reports often get lost and cannot be tracked. This is especially a big problem when its something that will take time to resolve.
If you need to report bugs, there is more details on the Bug Reporting page.
Email List
The email list for the developers and users of procps is found at http://www.freelists.org/archive/procps/ This email list discusses the development of procps and is used by distributions to also forward or discuss bugs.