Earlier quoted context omitted.
I’m using multiple search engines more and more. Possibly this is due to me usually bypassing google to avoid the ad laden hits. A view with search results from a few sources comes to mind as a solution. Another back burner project.
You can do this with browser search engines, but as a DuckDuckGo user, I can !bang search_term (`!gh`, `!github` to search in github.) Now, I think DuckDuckGo is very lacking in terms of Zero-click searching, but if I know where to get information I can !bang to it (e.g., `!hn what`) or if you're feeling luck `\hn what` will open the first search result. Much better than spending an afternoon setting up search engine…
What: A terminal tool to check what is taking up your bandwidth
171–180 of 190 posts
Re: What: A terminal tool to check what is taking up your bandwidth
#172Error: Failed to listen on network interface: No such file or directory (os error 2) on macOS. Anyone else getting this error?
On macOS 10.14.6 the command starts but the frames stays empty (silent error) because of SIP "Sandbox: lsof System Policy: deny(1)" Otherwise, really nice idea and work!
Re: What: A terminal tool to check what is taking up your bandwidth
#173Hey, I am the author of "what" and am very happy to hear people like this tool I made. :) "what" was my first real attempt at rust, and I love the project very much. That said, it is a hobby project - and so I will likely be a few days responding to all issues and contributions that came from this thread. "what" has already received some great contributions that are major parts of the code base. I would be very happy…
Re: What: A terminal tool to check what is taking up your bandwidth
#174 Error: Failed to listen on network interface: Operation not permitted (os error 1)Re: What: A terminal tool to check what is taking up your bandwidth
#175Bad 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 )
Re: What: A terminal tool to check what is taking up your bandwidth
#176Is sudo required? I get Error: Failed to listen on network interface: Operation not permitted (os error 1)
Re: What: A terminal tool to check what is taking up your bandwidth
#177I find the --raw output more useful than the interactive one. it scrolls away but I have time to read what's going on. The other one just disappears and is replaced by something else, which could be ok except sometimes there are seconds of useless black screen when nothing is going on. I suggest to never have blank screens. A suggestion for the raw output: add a timestamp at the beginning of the line. Probably HHMMSS…
Re: What: A terminal tool to check what is taking up your bandwidth
#178Earlier quoted context omitted.
This is the main problem keeping me from using this right now. I don't like installing binaries that conflict with system package names because I'm tin foil about stability and the super small chance that some installation/config script for some other package I rely on references `what` and breaks. @imsnif 2 questions: 1. Any chance you'd be willing to rename the package? I get it if not, but that would be so dope. 2…
1. Done. It's now known as "bandwhich" 2. This is in progress: https://github.com/imsnif/bandwhich/issues/9
Re: What: A terminal tool to check what is taking up your bandwidth
#179top of HN front page and without mentioning that it is written in Rust
Re: What: A terminal tool to check what is taking up your bandwidth
#180Name has changed to "bandwhich" as suggested here: https://old.reddit.com/r/rust/comments/ehl68y/what_a_termina...