ChromeBook@feddit.uk to Technology@beehaw.orgEnglish · 1 year agoMore useful command line linux toolsblog.safewebbox.comexternal-linkmessage-square8fedilinkarrow-up132
arrow-up132external-linkMore useful command line linux toolsblog.safewebbox.comChromeBook@feddit.uk to Technology@beehaw.orgEnglish · 1 year agomessage-square8fedilink
minus-squareLos@beehaw.orgMlinkfedilinkEnglisharrow-up2·1 year agoInteresting suggestion of btop. How does it compare to htop?
minus-squaresin_free_for_00_days@lemmy.onelinkfedilinkEnglisharrow-up3·1 year agoI like btop better just on an aesthetic level. But they all show the same shit as far as I can tell.
minus-squaremaynarkh@feddit.nllinkfedilinkEnglisharrow-up3·1 year agoReal programmers cat the data directly from /proc
minus-squareMangoPenguinlinkfedilinkEnglisharrow-up3·1 year agoPersonally I find btop really hard to glance at and see what’s happening, htop is much better for opening up and quickly checking what process is hogging CPU/RAM/IO/whatever.
Interesting suggestion of btop. How does it compare to htop?
I like btop better just on an aesthetic level. But they all show the same shit as far as I can tell.
Real programmers cat the data directly from /proc
Personally I find btop really hard to glance at and see what’s happening, htop is much better for opening up and quickly checking what process is hogging CPU/RAM/IO/whatever.