PRs for manpage 'netstat(1)'
This is an experimental report containing PRs for manpage 'netstat(1)' as of Thu Apr 24 07:38:16 2014 UTC. See notes.
PRs for manpage 'netstat(1)':
|o||2014/04/01||bin/188153||Interface name in the netstat(1) command is displayed as the first 7 characters, and the rest is cut off|
|o||2013/11/02||bin/183598||[patch] netstat(1): wrong display of humanized packets counter|
|o||2013/03/04||bin/176639||[patch] netstat(1) will display pcb table twice for any ip interfaces.|
|o||2011/11/15||docs/162587||doc||unclear/incomplete description of per-interface statistics flag in netstat(1)|
|o||2011/10/25||bin/161986||[patch] netstat(1): Interface auto-width in "netstat -rn"|
|o||2011/08/30||bin/160320||netstat(1): netstat -f inet6 does not output properly columns|
|o||2010/11/04||bin/151937||[patch] netstat(1) utility lack support of displaying rtt related counters of tcp sockets|
|o||2010/01/17||bin/142913||[patch] netstat(1) -w should produce error message if fed a negative value|
|s||2009/12/10||bin/141340||netstat(1): wrong netstat -w 1 output|
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.