Bug 102769 - netstat -i eth0 errors
Summary: netstat -i eth0 errors
Keywords:
Status: CLOSED DUPLICATE of bug 61113
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: net-tools
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-20 19:59 UTC by Ulf Zimmermann
Modified: 2015-03-05 01:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:58:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Ulf Zimmermann 2003-08-20 19:59:16 UTC
Description of problem:

Man page of netstat states:

       netstat {--interfaces|-i} [iface] [--all|-a] [--extend|-e[--extend|-e]]
       [--verbose|-v]      [--program|-p]      [--numeric|-n]      [--numeric-
       hosts][--numeric-ports][--numeric-ports] [--continuous|-c]

   --interface=iface , -i
       Display a table of all network interfaces, or the specified iface).


Version-Release number of selected component (if applicable):

net-tools-1.60-12

How reproducible:

Every time

Steps to Reproduce:

1. netstat -i eth0
2. netstat --interface=eth0
3.
    
Actual results:

1. netstat will print out usage message

2. netstat will print out usage message and in addition:

netstat: option `--interfaces' doesn't allow an argument

Expected results:

Print out the statistic of eth0 only

Additional info:

Comment 1 Phil Knirsch 2003-08-25 14:37:35 UTC
Just remembered, this has been entered before.

I've patched netstat over the weekend to work according to the manual and will
fix the usage output. The next net-tools rawhide version will contain the fix.

By default netstat will use all interfaces (as it used to do) but a single
interface to be monitored can be specified now, too (-ieth0 or --interface=eth0)

Read ya, Phil



*** This bug has been marked as a duplicate of 61113 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:58:10 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.