[HN Gopher] Btop++ is a power resource monitor for Linux
___________________________________________________________________
Btop++ is a power resource monitor for Linux
Author : feross
Score : 161 points
Date : 2021-09-23 20:31 UTC (2 days ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| einpoklum wrote:
| This looks very nice, but the compiler version requirement is
| very painful for those of us working on machines installed more
| than a year ago... GCC 10, ouch. I mean, newer versions are
| great, but when you don't control your machine's OS distribution,
| installing GCC 10 is not the most trivial thing to do.
| jcelerier wrote:
| You can just use a GCC docker image to build:
| https://hub.docker.com/_/gcc
| einpoklum wrote:
| No I can't... without an appropriate installation of docker
| and/or dependencies of docker.
|
| See: https://docs.docker.com/engine/security/rootless/#prereq
| uisi...
| zamadatix wrote:
| You don't control your device OS or otherwise have access
| to a machine you do, your OS does not offer modern
| packages, and you don't have the ability to otherwise pull
| in development toolchain resources.... yet it's supposed to
| be the projects problem you can't compile something started
| in 2021 from source on your older setup?
|
| I get your current situation is less than ideal for you but
| at some point you have to accept the project is not the
| source of painfulness associated with you trying to compile
| new apps from source, it's just the trigger.
| Naac wrote:
| On the surface looks like an improvement over htop ( which I've
| been using for 10+ years )
|
| But this is the kind of software that I would want to keep using.
| Will btop keep being supported? Is btop going to be available in
| practically all distros I use? Even currently on Arch its only in
| the AUR.
|
| Its also concerning there is btop[0] and bpytop[1]? I don't
| understand the difference.
|
| [0]https://github.com/aristocratos/btop
|
| [1]https://github.com/aristocratos/bpytop
| budzynski wrote:
| I think bpytop is the previous version writtten in Python.
| btop++ is a cpp re-write
| javchz wrote:
| The first thing I do with a Linux installation it's always add
| htop, and this it's the first time I feel the need to try
| something new in my routine.
| yjftsjthsd-h wrote:
| I like htop+dstat as nice compliments, but sadly dstat isn't
| universally available like htop and it's unmaintained
| 404mm wrote:
| htop and ncdu
| publicarray wrote:
| For me, it's been bottom
| https://github.com/ClementTsang/bottom and dua
| https://github.com/Byron/dua-cli for a while
|
| I've found some other cool CLIs written with rust at
| https://github.com/TaKO8Ki/awesome-alternatives-in-rust
| brightball wrote:
| htop and multitail are always tied for me.
| nerdponx wrote:
| https://linux.die.net/man/1/multitail
|
| I never heard of this one before. What's the benefit instead
| of doing this with Tmux?
| brightball wrote:
| I didn't know you could :)
| ggregoire wrote:
| > multitail
|
| You just made my day. I always open multiple ssh sessions
| just to display various logs at the same time.
|
| Seems like you can even docker-compose logs -tf | multitail
| -j.
|
| edit: I never took the time to learn tmux but after just
| watching a use case video, seems like you could achieve the
| same result with tmux indeed, as the other comment suggested.
| kzrdude wrote:
| tmux or gnu screen work fine (screen is sometimes installed
| when tmux is not)
| ohazi wrote:
| That terminal UI is a work of art...
| GekkePrutser wrote:
| Agreed. I thought gotop was cool but wow
| aidos wrote:
| It's really nice. That main main screen is giving me flashbacks
| to Doom.
| pridkett wrote:
| It's giving me some pretty heavy mid-90's BBS vibes. Even the
| menu with the big BTOP++ logo reminds me of a main menu on a
| BBS.
|
| Now if we can just slow it down to 240 characters/second to
| simulate the real experience. It won't be authentic unless it
| also slows down when you're changing colors because of the ANSI
| escape codes.
| bloopernova wrote:
| Quick word of warning, if you download it: The release archive
| doesn't create a directory, just untars into $CWD. So do this:
| mkdir btop cd btop tar xjvf
| ~/Downloads/btop.....tbz ./install.sh
|
| Apart from that, it looks really, really nice. I like it a lot!
| matoro wrote:
| I use atool (https://www.nongnu.org/atool/) for unpacking
| random archives - it abstracts away all formats including
| zip/rar/7z, compression and also guarantees that nothing is
| ever extracted into $CWD.
| linsomniac wrote:
| Gotta check that out, thanks for the tip!
| iudqnolq wrote:
| I use `unp` for the same thing. `-u` extracts into a
| directory.
| isclever wrote:
| This is why I have trust issues when github pulling or
| exploding a tar.
| OJFord wrote:
| Maybe it's just me, but this seems like the more obvious
| behaviour? Personally I'd typically extract in /tmp/relevant-
| name, and sometimes that results in /tmp/relevant-
| name/relevant-name.
|
| Doesn't seem a big deal or require/cause trust issues to me.
|
| (And when I create one, I always have to check/look up what
| happens, so it doesn't surprise me that a variety of things
| get done at all.)
| bityard wrote:
| It's been common convention for decades that if you
| distribute a source tarball of something, that everything
| inside is inside a directory named foobar-1.0 where
| 'foobar' is the project name and 1.0 is the version.
|
| Not everyone does this, of course, but it's nice when they
| do. Because it means you can just wget the file into a dir
| and untar it without worrying about it messing up whatever
| is already there. Also handy for putting different versions
| of the project side-by-side.
| OJFord wrote:
| Ok, but like you say it's a mixed bag - _I_ 'wget the
| file into a dir and untar it without worrying about it
| messing up whatever is already there', because nothing
| is, it's a mktemp -d or manual equivalent.
| wyldfire wrote:
| That was typical on DOS/Windows when distributing ZIP
| archives, for a long time.
|
| But on *nix systems, the idiom for tarballs usually
| includes a directory containing all of the contents.
|
| > (And when I create one, I always have to check/look up
| what happens, so it doesn't surprise me that a variety of
| things get done at all.)
|
| True - I usually do a `tar tf foo.tar.xz |head` to get a
| quick peek at the archive. This generally avoids the
| problem of dumping a bunch of files into the current
| directory.
| nerdponx wrote:
| I always check the contents with -t before extracting.
| jancsika wrote:
| Author: please make your program name an acronym for
|
| Bower Tesource Onitor for Pinux
| yewenjie wrote:
| I have been using glances for a terminal sysmon but I don't like
| that it eats so much RAM. Can someone please recommend a system
| monitor that is easy to comprehend and less resource hungry?
|
| I am also curious about below [0] since it came up recently.
|
| [0] https://github.com/facebookincubator/below
| jeffbee wrote:
| Kinda depends on what you want to know and how much memory you
| think is too much. Implementations range from sar to atop to
| netdata and many others.
| sk5t wrote:
| 'nmon' doesn't get much attention, but it feels lightweight (I
| haven't tested if it really is) -
| https://en.wikipedia.org/wiki/Nmon
| smoldesu wrote:
| Maybe bottom[0]? I use bpytop but probably wouldn't recommend
| it on account of how heavy it is. I remember bottom being
| pretty lightweight when I used it, without sacrificing
| readability.
|
| [0] https://github.com/ClementTsang/bottom
| btach wrote:
| Looks almost identical to bpytop. Super neat!
| biglost wrote:
| For me it's enough iotop + bpytop + htop
| codetrotter wrote:
| The readme for bpytop links to btop++
|
| https://github.com/aristocratos/bpytop
|
| It says:
|
| > The Linux version of btop++ is complete. Released as version
| 1.0.0
|
| My impression is that btop++ is the successor to bpytop. Or
| even if bpytop continues to be maintained that they intend for
| most people to use btop++ instead going forward.
___________________________________________________________________
(page generated 2021-09-25 23:00 UTC)