mirrors/procps
0
0
Fork 0
mirror of https://gitlab.com/procps-ng/procps.git synced 2024-11-23 10:03:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
3,867 Commits 2 Branches 31 Tags 22 MiB
C 97.2%
Makefile 1%
M4 0.9%
Shell 0.9%
ba70e47c33
Go to file
Roman Žilka ba70e47c33 watch: Display lowheader when exiting on -e 
* Display lowheader when exiting on -e.
* Only refresh() screen when cmd was run this pass through the main loop in
  main(). Till now the first line of header was refreshed on-screen each time
  the main loop restarted. That was confusing when resizing with -r: current
  time in header would update after a resize, suggesting that the cmd was
  executed at that time, while it actually wasn't and the cmd output shown
  would be invalid: either it'd be old or presented as empty (when clear() used
  to be part of the main loop prologue).

Signed-off-by: Craig Small <csmall@dropbear.xyz>
2023-10-06 16:53:26 +11:00
doc misc: Move Documentation to doc 2022-08-29 18:38:52 +10:00
library str*dup()->xstr*dup() where needed; library: openproc(): avoid closedir(NULL) 2023-10-06 05:03:30 +00:00
local watch: -e passes command's exit code on to environment 2023-10-06 16:53:13 +11:00
man watch: Included cmd exitcode in 2nd line of header 2023-10-06 16:53:15 +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 watch: Display lowheader when exiting on -e 2023-10-06 16:53:26 +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 watch: -e passes command's exit code on to environment 2023-10-06 16:53:13 +11:00
NEWS NEWS: acknowledge fix for the lost tasks ps issue #304 2023-10-05 07:28:32 +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

README.md

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.