What: A terminal tool to check what is taking up your bandwidth

Post by guytv » Mon, Dec 30, 2019, 12:48 PM UTC

avoro wrote: post #19

What can be a reason if on MacOS it does not capture traffic? I see empty panels. Tried to run with and without `sudo`.

Post by hittaruki » Mon, Dec 30, 2019, 12:57 PM UTC

bicolao wrote: post #31

jxf wrote: post #7

Earlier quoted context omitted.

They are similar but they answer different questions. By default, iftop will tell you "this network interface on your machine is talking a lot to ycombinator.com". But you don't necessarily know which processes are doing the most talking collectively. This will tell you "Firefox process 4567 is talking a lot ycombinator.com" and you'll know whether 4567 is also one of the chattiest talkers right now.

> This will tell you "Firefox process 4567 is talking a lot ycombinator.com" and you'll know whether 4567 is also one of the chattiest talkers right now. But that's what nethogs does.

Post by rotten » Mon, Dec 30, 2019, 1:00 PM UTC

anilgulecha wrote: post #34

lazyjones wrote: post #26

Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)

This is in the top class of utilities (htopm etc). A good name could probably be bwtop, or tcptop or iftop. Actually I searched for these, and turns out iftop exists! ( https://linux.die.net/man/8/iftop )

Post by mellosouls » Mon, Dec 30, 2019, 1:02 PM UTC

hnarn wrote: post #2

What are the main differences to something like nethogs or iftop?

Post by steveklabnik » Mon, Dec 30, 2019, 1:16 PM UTC

StavrosK wrote: post #68

djsumdog wrote: post #53

Earlier quoted context omitted.

This is one of the biggest problems I've had with any neat Rust thing posted up here. The language changes a lot. I have rust/cargo 1.37.0 installed (it's the latest marked stable in Gentoo) and adler32 v1.0.4 fails to compile with "`core::slice:: ::len` is not yet stable as a const fn". I'm installing 1.40.0 from the unstable tree to see if that will build it. I've had situations where I'm either not on the latest v…

Agreed, and I had the same problem. It seems like an easy fix to add a requires_rust_version thing in Cargo.toml, and devs could at least set it to "the version I'm currently using" so we know it's guaranteed to build on that.