PRs for manpage 'systat(1)'
This is an experimental report containing PRs for manpage 'systat(1)' as of Fri May 30 07:39:37 2014 UTC. See notes.
PRs for manpage 'systat(1)':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2013/09/27 | bin/182448 | melifaro | systat(1): systat -if have invalid counters with 10Gb/s traffic |
o | 2013/06/29 | bin/180101 | systat(1) / vmstat(8): command 'only' only displays first of multiple drives | |
o | 2011/09/02 | bin/160412 | wrong value in systat(1) | |
s | 2006/07/09 | bin/99973 | systat(1): systat -ifstat traffic counter overflow | |
o | 2004/02/13 | bin/62766 | systat(1) -vm does not work on diskless machines | |
o | 2003/11/12 | bin/59220 | obrien | [patch] systat(1) device select (:only) broken |
o | 2001/12/10 | bin/32667 | systat(1) waste too much time reading input | |
s | 1996/12/02 | bin/2137 | [vm] systat(1) total vm statistics are bad |
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.