Go to file
Jim Warner 9dc281fe4b library: include the 'docker' containers in <pids> api
This commit makes a task's 'docker' container id (both
full and abbreviated) available within the <pids> API.

It is patterned after that 'lxc' container logic which
tracks ids already seen so as to avoid repeated malloc
plus free calls. It should be noted, however, that the
'docker' ids do not proliferate like those others may.

In implementing the addition, the 'readproc/task' code
had to be tweaked a little. The code for PROC_FILL_LXC
and PROC_FILL_DOCKER now share a buffer containing the
cgroup contents so as to avoid a second file2str call.

[ yes, each container extraction routine may corrupt ]
[ that buffer. and yes, a caller may request both of ]
[ those enums (LXNAME and DOCKER_ID) simultaneously. ]
[ but, a task can be in only one container at a time ]
[ so the buffer would get whacked at most just once. ]

Signed-off-by: Jim Warner <james.warner@comcast.net>
2023-12-26 20:55:24 +11:00
doc misc: Move Documentation to doc 2022-08-29 18:38:52 +10:00
library library: include the 'docker' containers in <pids> api 2023-12-26 20:55:24 +11:00
local build-sys: add 'units.h' to the local/Makefile.am file 2023-10-16 07:13:36 +11:00
man top: accommodate a separate 'disk sleep' in <pids> api 2023-12-26 20:55:24 +11: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: accommodate a separate 'disk sleep' in <pids> api 2023-12-26 20:55:24 +11:00
testsuite testsuite: skip tests where relevant binaries aren't built 2023-10-04 08:56:22 +00:00
.gitignore nls: Update the man-po logic 2022-11-10 21:52:19 +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 INSTALL.md: Replace blockquotes with code blocks 2020-04-24 18:56:16 +10:00
Makefile.am Slabtop - add --human flag for human-readable units 2023-10-11 17:55:09 +11:00
NEWS NEWS: acknowledged separate 'disk sleep' in <pids> api 2023-12-26 20:55:24 +11:00
README.md misc: Fix typo 2021-10-14 07:57:27 +11: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 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:

  1. Your distribution's 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.
  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. 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.