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.
2532b5d2dd
The lstart field has been converted to use the strftime() function so that it uses the locale. A new option -D allows the user to define the format that would want this field to show. This may mean the field will be longer than it should be, especially for French locales and the user defined field, but the field length can be specified too. --- This commit started off making all the relevant fields use the locale correctly so it could solve #226 as well. The issue is there an implied restriction (or not) around strftime("%b") and probably strftime("%a") for abbrievated month and day names respectively. English, and some/most other languages put an additional restriction that all abbreviations are 3 characters long. The problem is, not all languages do this. French is a good example: janv. févr. mars avril mai juin juil. août sept. oct. nov. déc. Maybe strip the . at the end? That helps for some months, not all Maybe take the first three characters? Several wide languages will have big issues Maybe convert wide, get wcslen then use that. Even after that June "juin" and July "juil" are both "jui". So, anything that uses the month (bsdstart,start) use ctime which doesn't use locale. That solves the length issue. stime does, which means it has this issue but its been like that for years. You get stuff like this: janv.13 482261 00:00 1151918 2022 1458628 06:12 1957584 The only way to fix that would be to a)Make the field two characters longer b)Convert it back to ctime() which means everyone else loses. This could have be oh-so easy if everyone made %b and %a three (wide) characters everywhere. References: procps-ng/procps#228 procps-ng/procps#226 Signed-off-by: Craig Small <csmall@dropbear.xyz> |
||
|---|---|---|
| doc | ||
| library | ||
| local | ||
| man | ||
| po | ||
| po-man | ||
| src | ||
| testsuite | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| AUTHORS | ||
| COPYING | ||
| COPYING.LIB | ||
| ChangeLog | ||
| INSTALL.md | ||
| Makefile.am | ||
| NEWS | ||
| README.md | ||
| autogen.sh | ||
| configure.ac | ||
| create-man-pot.sh | ||
| sysctl.conf | ||
| translate-man.sh | ||
README.md
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 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.
- 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.