[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140422154616.4e4eb445@nehalam.linuxnetplumber.net>
Date: Tue, 22 Apr 2014 15:46:16 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Decotigny <decot@...glers.com>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2 v1] iproute2: show counter of carrier on<->off
transitions
On Wed, 2 Apr 2014 09:19:00 -0700
David Decotigny <decot@...glers.com> wrote:
> This patch allows to display the current counter of carrier on<->off
> transitions (IFLA_CARRIER_CHANGES, see kernel commit "expose number of
> carrier on/off changes"):
>
> ip -s -s link show dev eth0
> ...
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 etc.
> link/ether ............ brd ff:ff:ff:ff:ff:ff
> RX: bytes packets errors dropped overrun mcast
> 134705 758 0 0 0 0
> RX errors: length crc frame fifo missed
> 0 0 0 0 0
> TX: bytes packets errors dropped carrier collsns
> 77374 731 0 0 0 0
> TX errors: aborted fifo window heartbeat
> 0 0 0 0
> link: carrier_changes 4
>
I wonder if putting it under TX errors would make sense.
This is where Juniper classifies the error, and it would also
fit on same line, avoiding adding more clutter.
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 etc.
link/ether ............ brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
134705 758 0 0 0 0
RX errors: length crc frame fifo missed
0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
77374 731 0 0 0 0
TX errors: aborted fifo window heartbeat transition
0 0 0 0 4
The risk is break some screen scraping script, but that doesn't
seem to be that big an issue for adding one column.
The columns also need some re-aligning here but that is different
correctness issue.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists