Go to file
Jim Warner 1b92eb1b7f top: some final tweaks for that keys_bottom() function
When the keys_bottom() function was introduced in that
commit shown below, some elements reflected an earlier
version when under development. Now there isn't a need
for a static integer nor the saving of a return value.

Reference(s):
. Jul, 2024 - introduced keys_bottom
commit ad77827e9c

Signed-off-by: Jim Warner <james.warner@comcast.net>
2024-08-27 06:27:52 +10:00
doc misc: Move Documentation to doc 2022-08-29 18:38:52 +10:00
library library: improve code employing the search.h functions 2024-07-26 19:35:38 +10:00
local library: Add capability naming 2024-07-01 23:06:22 +10:00
man top: just a couple of minor tweaks to the man document 2024-08-27 06:27:52 +10:00
po nls: Update translation files 2023-08-31 19:47:01 +10:00
po-man nls: Update translation files 2023-08-31 19:47:01 +10:00
src top: some final tweaks for that keys_bottom() function 2024-08-27 06:27:52 +10:00
testsuite testsuite: Test new ps -o fds option 2024-05-12 18:19:18 +10:00
.gitignore hugetop: Minor adjustments 2024-01-31 18:03:52 +11:00
.gitlab-ci.yml test: Update gitlab CI YAML to use shared runner 2016-04-20 22:20:55 +10:00
AUTHORS Changed git site to gitlab 2015-05-10 14:57:50 +10:00
autogen.sh misc: Move all binaries to src 2022-08-29 18:29:28 +10:00
ChangeLog Changed git site to gitlab 2015-05-10 14:57:50 +10:00
configure.ac build-sys: only define USE_PROC_CTTY when under Cygwin 2023-10-05 07:28:32 +11:00
COPYING license: update FSF addresses 2012-03-04 08:04:24 +11:00
COPYING.LIB miscellaneous: clean up trailing whitespace once again 2013-04-07 18:05:01 +10:00
create-man-pot.sh build-sys: Rearrange the manual pages 2022-08-29 18:07:43 +10:00
INSTALL.md Minor wording changes to MarkDown documents 2024-04-02 08:54:39 +00:00
Makefile.am library: Add capability naming 2024-07-01 23:06:22 +10:00
NEWS vmstat: Add page allocation to --stats 2024-07-20 13:01:29 +10:00
README.md Minor wording changes to MarkDown documents 2024-04-02 08:54:39 +00:00
sysctl.conf misc: Add some link examples to sysctl.conf (catch up) 2018-05-06 07:19:38 +10:00
translate-man.sh build-sys: Rearrange the manual pages 2022-08-29 18:07:43 +10:00

build status 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 kernel data structures. The utilities provided by procps focus on the structures that describe processess running on the system.

The following utilities are provided by procps:

  • free - Report the amounts of free and used memory in the system
  • hugetop - Report hugepage usage of processes and the system as a whole
  • 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 the memory map of a process
  • ps - Report process information including PID and resource usage
  • pwdx - Report the current working 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 three ways to submit bugs or feature requests:

  1. Your Linux distribution's bug reporter. If you are using Linux distribution packages 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.
  2. GitLab Issues - To the left of this page is the issue tracker. You can report bugs here.
  3. Email list - We have an email list (see below) where you can report bugs. A shortcoming of this method is that such bug reports often get lost and cannot be tracked. This is especially problematic when the report conerns 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.