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.
Go to file
Jim Warner 9ea0021070 ps: don't use '+' truncation indicator with multi-byte
The ps program generally supports multi-byte sequences
in strings representing user and group names. However,
should a multi-byte sequence span the maximum width of
a column, the '+' inserted by ps to signify truncation
will corrupt that sequence, misaligning the text line.

Unfortunately, there's insufficient info returned from
the escape_str function (who calls escape_str_utf8) to
provide a robust response. So, this commit will revert
to the old standby of displaying a number when the '+'
character would've corrupted that multi-byte sequence.

Signed-off-by: Jim Warner <james.warner@comcast.net>
2017-10-02 22:23:13 +11:00
contrib
doc
Documentation
include
lib kill: -l space between name parses correctly 2017-05-22 22:15:59 +10:00
man-po
misc
po
proc library: fixed miscellaneous whitespace/comment issues 2017-10-01 22:25:18 +11:00
ps ps: don't use '+' truncation indicator with multi-byte 2017-10-02 22:23:13 +11:00
testsuite Port of merge request 49 to newlib 2017-08-19 23:05:22 +10:00
top top: extend utf-8 multi-byte support to users & groups 2017-10-01 22:35:12 +11:00
.gitignore Port of merge request 49 to newlib 2017-08-19 23:05:22 +10:00
.gitlab-ci.yml
AUTHORS
autogen.sh
ChangeLog
configure.ac Port of merge request 49 to newlib 2017-08-19 23:05:22 +10:00
COPYING
COPYING.LIB
create-man-pot.sh
free.1
free.c misc: adapt 3 programs to some enum changes, <meminfo> 2017-06-04 21:36:23 +10:00
INSTALL.md
kill.1
kill.c kill: -l space between name parses correctly 2017-05-22 22:15:59 +10:00
Makefile.am Port of merge request 49 to newlib 2017-08-19 23:05:22 +10:00
NEWS NEWS: acknowledged top's multi-byte support extensions 2017-10-01 22:26:35 +11:00
pgrep.1
pgrep.c
pidof.1
pidof.c
pkill.1
pmap.1
pmap.c
pwdx.1
pwdx.c
README.md
skill.1
skill.c Port of merge request 49 to newlib 2017-08-19 23:05:22 +10:00
slabtop.1
slabtop.c
snice.1
sysctl.8
sysctl.c Avoid confusing messages caused by EIO on reading 2017-08-20 09:22:58 +10:00
sysctl.conf
sysctl.conf.5
tload.1
tload.c Fix out of boundary write on 1x1 terminals 2017-08-19 23:10:26 +10:00
translate-man.sh
uptime.1
uptime.c
vmstat.8
vmstat.c vmstat: Fix alignment for disk partition format 2017-09-25 09:24:42 +10:00
w.1
w.c
watch.1
watch.c

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 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.
  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.