Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide complete /proc/net/dev output #183

Closed
ptalbert opened this issue Oct 5, 2015 · 6 comments
Closed

Provide complete /proc/net/dev output #183

ptalbert opened this issue Oct 5, 2015 · 6 comments
Assignees

Comments

@ptalbert
Copy link
Collaborator

ptalbert commented Oct 5, 2015

Currently, xsos --netdev does not show RX Frame and TX FIFO counters from /proc/net/dev. Can these be added to the output?

Maybe too complex, but to limit the width of the output perhaps xsos would only print any given error counter column if any of the rows are non-zero?

@ryran
Copy link
Owner

ryran commented Oct 6, 2015

Not too complex..just possibly confusing, but yeah I'll try it out.

On Mon, Oct 5, 2015, 14:45 ptalbert [email protected] wrote:

Currently, xsos --netdev does not show RX Frame and TX FIFO counters from
/proc/net/dev. Can these be added to the output?

Maybe too complex, but to limit the width of the output perhaps xsos would
only print any given error counter column if any of the rows are non-zero?


Reply to this email directly or view it on GitHub
#183.

@ryran ryran self-assigned this Feb 10, 2016
@ryran
Copy link
Owner

ryran commented Feb 16, 2016

Done and ready for the next release which is long overdue but I'm debating whether to do this:

netdev split

Or this:

netdev wide

The latter basically requires you to use the -y option -- i.e., to always pipe output to less -S. FEEDBACK WANTED.

@jbainbri
Copy link

Wow nice! Please do the first one, because the second option is too wide.

@Aftermath
Copy link

Agreed, with option 1!

@ryran
Copy link
Owner

ryran commented Feb 16, 2016

@jbainbri just blew my mind.

like, if the packet was TxDropped, it wasn't Tx'ed, so you'd increment
the dropped counter and not the Tx counter

Everything is a lie. OMG I've been doing it wrong all along.

@evdanil
Copy link

evdanil commented Feb 16, 2016

option 1

@ryran ryran closed this as completed in 4b5298a Feb 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants