I have a list of about 20 or 30 applications — mostly console-based — that I want to take a crack at in the next few weeks, once the end-of-year break starts. One of them I took a stab at today though, mostly because it’s tiny, but also because the output is rather promising. The problem is, I’m not really sure what to call it. Take a look for yourself.
Well, to be perfectly honest about it, this one is (a) simple, (b) straightforward, (c) resizes itself nicely when the terminal is adjusted, (d) uses color, and (e) is reasonably flexible.
In all seriousness. It’s a network monitor, and it doesn’t require root access to watch an access point. It only does one thing, requires almost nothing in the way of dependencies, the display is colorized and attractive, it doesn’t mind if the console changes shape while it’s running, and you can adjust the max levels on both sides to properly see what’s going up and down.
Any one of the net monitors I mentioned before had small, nitpicking faults. iftop is fantastic, but rather droll and requires sudo or root permission to watch a network point. slurm is likewise excellent, but doesn’t do well in terminal sizes outside the ordinary, and sometimes has a panic attack when resized. iptraf is good, but lacks that certain … “something.”
I could go on. My point here is this one is easy to build, easy to configure (with only three flags), easy to resize, easy on the eyes and easy to run. I don’t want to hold up a 6-year-old (according to the timestamps in the tarball) program as some sort of example of application perfection, but this one is a pretty good example.
If only I knew what it was called. The tarball is called “net,” the executable is called “monitor.” You tell me what it’s supposed to be called.