3 ms·

Very, very awesome! I love the per process table. How does that work? CBM was a fine tool [0]. I think it's been basically abandoned though. It does only do pe

Very, very awesome! I love the per process table. How does that work? CBM was a fine tool [0]. I think it's been basically abandoned though. It does only do per interface, but it seems like an earlier simpler iteration of this type of tool. It works by reading the stat tables in /proc/net/dev I'd just throw our something I wrote a long time ago called fsbm [1] (fucking small bandwith monitor) which was a rewrite of CBM without curses. useful for logging to a file or to something without NCURSES support. Along the way I added support for network namespaces and just general other stuff. I use it frequently. You can pump it into i3-bar for example or such and such [0] https://github.com/resurrecting-open-source-projects/cbm https://github.com/resurrecting-open-source-projects/cbm [1] https://git.ceux.org/fsbm.git/tree/fsbm.c https://git.ceux.org/fsbm.git/tree/fsbm.c

freedomben 3y ago
I'm not sure how it works beyond that it reads /proc, but whatever it does it uses a whole lot more compute than nethogs does (which also displays per process and also uses /proc as the information source). This is fine for most of my machines, but for lower-specced machines I'll probably have to stick with nethogs[1] [1]: https://github.com/raboof/nethogs https://github.com/raboof/nethogs
- mr337 3y ago
  If it the popey from podcasts he used to work at Canonical. Actually looking at this confused, popey also came up with the snap removal tool that is handy https://github.com/popey/unsnap https://github.com/popey/unsnap Maybe he has a love hate relationship with snaps lol Edit: added gh info
  - freedomben 3y ago
    Yeah I would strongly bet it is the same Popey from the JB podcasts. Last I heard him he was pretty pro-Snap and was Snapping different projects for people, so this is completely in-line with my expectations. Seems pretty unlikely to be a coincidence :-)

freedomben 3y ago

I'm not sure how it works beyond that it reads /proc, but whatever it does it uses a whole lot more compute than nethogs does (which also displays per process and also uses /proc as the information source). This is fine for most of my machines, but for lower-specced machines I'll probably have to stick with nethogs[1] [1]: https://github.com/raboof/nethogs https://github.com/raboof/nethogs

mr337 3y ago
If it the popey from podcasts he used to work at Canonical. Actually looking at this confused, popey also came up with the snap removal tool that is handy https://github.com/popey/unsnap https://github.com/popey/unsnap Maybe he has a love hate relationship with snaps lol Edit: added gh info
- freedomben 3y ago
  Yeah I would strongly bet it is the same Popey from the JB podcasts. Last I heard him he was pretty pro-Snap and was Snapping different projects for people, so this is completely in-line with my expectations. Seems pretty unlikely to be a coincidence :-)