PRs for manpage 'vmstat(8)'
This is an experimental report containing PRs for manpage 'vmstat(8)' as of Fri May 30 07:39:59 2014 UTC. See notes.
PRs for manpage 'vmstat(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/12/13 | docs/184755 | doc | The vmstat(8) manualpage synopsis doesn't show all optional parameters |
| o | 2013/06/29 | bin/180101 | systat(1) / vmstat(8): command 'only' only displays first of multiple drives | |
| o | 2011/12/28 | bin/163680 | vmstat(8): negative values in vmstat -z | |
| o | 2011/12/22 | bin/163547 | vmstat(8): vmstat -i show AVG rate instead of rate | |
| o | 2010/12/01 | bin/152738 | [patch] vmstat(8), printhdr() doesn't work correctly with -p option under multiple CPUs | |
| o | 2010/01/17 | bin/142911 | [patch] vmstat(8) -w should produce error message if fed a negative value | |
| a | 2001/09/05 | bin/30360 | vmstat(8) returns impossible data |
Notes
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.