FS#36538 - nethogs defaults to eth0 which is not present on systemd based systems
Attached to Project:
Community Packages
Opened by Andrew Cowie (afcowie) - Thursday, 15 August 2013, 04:42 GMT
Last edited by Kyle Keen (keenerd) - Friday, 16 August 2013, 14:05 GMT
Opened by Andrew Cowie (afcowie) - Thursday, 15 August 2013, 04:42 GMT
Last edited by Kyle Keen (keenerd) - Friday, 16 August 2013, 14:05 GMT
|
Details
nethogs assumes a default interface of eth0. This is no
longer useful in a systemd world. Is there anyway we can
have it default to the currently [most (sic)] up interface?
Pain in the ass to have to do `ip addr` to dig out the
'enp0s25' string which is my network card on today's
computer.
AfC |
This task depends upon
Closed by Kyle Keen (keenerd)
Friday, 16 August 2013, 14:05 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed in upstream's cvs.
Friday, 16 August 2013, 14:05 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed in upstream's cvs.
I suggest you write an alias.
There is no way to hardcode a guess as to what your interfaces will be. I see two possible solutions:
1) Remove the default. Make nethogs error when there is no specified interface. Aka, BOFH solution.
2) Make the default smarter. Since it can't guess which of your ifaces are being used, the default should display traffic for all of them.
You can fake the second with
nethogs $(ip -4 -6 -o a | cut -f 2 -d ' ')
Personally I don't want to write either of these today. I suggest you try requesting the feature upstream.
I will close this tomorrow-ish unless there is meaningful input, such as an upstream feature request to link.