18e5aecd2b
Way back in November of 2011, the library was equipped with an overridable error message handler function. It was done expressly for a program like top which alters the tty. But that support was withdrawn shortly after. This was all done in the lead up to v3.3.2. That's the release where NLS support was added and it represented a hectic time. In hindsight, the changes went too far. So this commit, in a minimal fashion, restores ability to address a potential fatal library error. After all, any properly behaving library would never unilaterally subject a caller to a stderr message and then an exit. [ when exposing 1 variable in libprocps.sym, 2 other ] [ existing symbols were repositioned alphabetically. ] Reference(s): . generalized library memory provisions commit 7126cc4491847ce5d50e603fe48666f94bfc60bf . top exploit library memory provisions commit 88087ec5a5968304d6461be2c2fbe05885ffdad8 . library xalloc type functions made private commit 2865ded64e72e0bec721dad9b442dab0899ee2b0 . restored prior top memory logic commit 05f5deb97c454b3558892ff4266efc81547f88d5 Signed-off-by: Jim Warner <james.warner@comcast.net>
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 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.
- 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.