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.
29f0a674a8
After the stage had been set in the previous patch, in this patch we will actually implement those background updates via 3 separate threads. The design was simple: . the do-while loops have now been made truly infinite . 2 semaphores per thread allow needed synchronization . 1 semaphore will provide for each thread to sem_wait . 1 semaphore will provide for display o/p to sem_wait . and all 3 thread's program name was made descriptive A complication was the potential for a signal directed to one of our new threads. Rather than having a thread try to deal with such signals, we pass a mask with all signals blocked at pthread_create time. Thereafter any subsequent signals are forwarded to the parent thread. [ also sigprocmask was exchanged for pthread_sigmask ] [ since warned about use "in multithreaded process". ] [ plus we also modified each of those POSIX comments ] [ about 2004 to agree with current signal-safety(7). ] Sadly, after all this effort there were no performance benefits to having separate threads. In fact there was a measurable performance degradation when running with ever smaller delay intervals. But even with a delay of 1/10 second the 'real' cost increase is only about 1%. There is one way whereby any additional costs might be eliminated (at least seemingly). One could introduce 2 separate sets of contexts for each of those 3 threads. Then retrieval & display could be overlapped. However, the resulting display wouldn't represent the real-time results. Rather it would be stale by 1 delay interval. Signed-off-by: Jim Warner <james.warner@comcast.net> |
||
|---|---|---|
| contrib | ||
| doc | ||
| 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 | ||
| kill.c | ||
| Makefile.am | ||
| NEWS | ||
| pgrep.1 | ||
| pgrep.c | ||
| pidof.1 | ||
| pidof.c | ||
| pidwait.1 | ||
| pkill.1 | ||
| pmap.1 | ||
| pmap.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.