top of HN front page and without mentioning that it is written in Rust
What: A terminal tool to check what is taking up your bandwidth
51–60 of 190 posts
Re: What: A terminal tool to check what is taking up your bandwidth
#52Is this the future? I am setting this up on my macOS, and before I could 'cargo add' anything I had to 'brew install rust'. Now it is downloading and compiling lots and lots of dependencies.
you only will need to "cargo install " now that you've got the rust compiler and cargo installed on your machine
Re: What: A terminal tool to check what is taking up your bandwidth
#53Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)
cargo install what (fails) Package `trust-dns-proto v0.18.0` does not have these features: `tokio-compat` (MacOS 10.15.2)
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 version of rust, or I'm on too current a version of rust, which deprecated/removed some feature needed for a dependency. I'm not sure if devs can define their min/max versions, but that kinda check should probably be done before cargo starts building packages.
Re: What: A terminal tool to check what is taking up your bandwidth
#54Can I now trash iftop and nethogs?
Re: What: A terminal tool to check what is taking up your bandwidth
#55What can be a reason if on MacOS it does not capture traffic? I see empty panels. Tried to run with and without `sudo`.
Same here. Tried different interfaces. Nothing.
Re: What: A terminal tool to check what is taking up your bandwidth
#56Earlier quoted context omitted.
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 )
iftop is a remarkably useful utility. It's often one of the first things I install on new openwrt installations.
Ever since I installed SQM on openwrt, I don’t really care what’s using the bandwidth anymore since it doesn’t impact any other users on the network. :) It’s true though that iftop is a very useful tool.
Re: What: A terminal tool to check what is taking up your bandwidth
#57Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)
When the bb is slow, it might be because someone is "hogging" the bb - so maybe "whathog"?
or "wiccapig/wicpig" (whichhog) ;-)
Re: What: A terminal tool to check what is taking up your bandwidth
#58Plot twist. It's the tool
Would be interesting to know how many people actually look at the source before they compile and run random repos posted here.
Re: What: A terminal tool to check what is taking up your bandwidth
#59Error: Failed to listen on network interface: No such file or directory (os error 2) on macOS. Anyone else getting this error?
Yep. checked on two different machines connecting to two different networks.
Re: What: A terminal tool to check what is taking up your bandwidth
#60Is this the future? I am setting this up on my macOS, and before I could 'cargo add' anything I had to 'brew install rust'. Now it is downloading and compiling lots and lots of dependencies.
you only will need to "cargo install " now that you've got the rust compiler and cargo installed on your machine
Indeed. I couldn't get the tool working once it was downloaded and compiled. iftop works fine.