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.
893793a8c4
I thank Guido Jäkel for raising the issue cited in the merge request referenced below. While restoring 1 line of code would produce the desired results, it does not address the root cause of that problem he experienced. The variable 'smp_num_cpus' was set by libprocps via a sysconf(_SC_NPROCESSORS_ONLN) call. It was supposed to represent total number of processors currently online. It also served as the position in the Cpu_tics[] array where the /proc/stat line #1 (cpu summary) was stored. The variable 'Cpu_faux_tot' was valued by top based on total individual cpus parsed from the /proc/stat file. It serves as a fence post for Cpu_tics[] array access. The problem Guido experienced results from a disparity between those 2 variables, plus one instance where the wrong variable was used in the summary_show() routine. . Here is the real culprit, the actual incorrect code: . summary_hlp(&Cpu_tics[Cpu_faux_tot], N_txt(WORD_a... Which always should have been represented in this way: . summary_hlp(&Cpu_tics[smp_num_cpus], N_txt(WORD_a... ------------------------------------------------------ The above 'disparity' might arise in any system when a cpu is taken offline since there's a 3 second delay in cpu and memory refreshes in an effort to reduce costs. Usually this particular condition will be short lived. However, there is a more persistent problem under lxc. If a host cpu is taken offline and then brought online again, within the container sysconf returns the proper number of online processors. But, /proc/stat does not! Sadly, I've yet to find a way to coax a container into refreshing its /proc/stat, short of reboting the host. [ might that represent a potential bug in lxc logic? ] Reference(s): https://gitlab.com/procps-ng/procps/merge_requests/82 Signed-off-by: Jim Warner <james.warner@comcast.net> With-thanks-to: Guido Jäkel <G.Jaekel@DNB.DE> |
||
|---|---|---|
| contrib | ||
| Documentation | ||
| include | ||
| lib | ||
| man-po | ||
| misc | ||
| po | ||
| proc | ||
| ps | ||
| testsuite | ||
| top | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| COPYING.LIB | ||
| create-man-pot.sh | ||
| free.1 | ||
| free.c | ||
| INSTALL.md | ||
| kill.1 | ||
| Makefile.am | ||
| NEWS | ||
| pgrep.1 | ||
| pgrep.c | ||
| pidof.1 | ||
| pidof.c | ||
| pkill.1 | ||
| pmap.1 | ||
| pmap.c | ||
| procio.c | ||
| pwdx.1 | ||
| pwdx.c | ||
| README.md | ||
| skill.1 | ||
| skill.c | ||
| slabtop.1 | ||
| slabtop.c | ||
| snice.1 | ||
| sysctl.8 | ||
| sysctl.c | ||
| sysctl.conf | ||
| sysctl.conf.5 | ||
| tload.1 | ||
| tload.c | ||
| translate-man.sh | ||
| uptime.1 | ||
| uptime.c | ||
| vmstat.8 | ||
| vmstat.c | ||
| w.1 | ||
| w.c | ||
| watch.1 | ||
| watch.c | ||
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.