causes Posted October 2, 2014 Report Share Posted October 2, 2014 Post here useful commandline tools. * app-arch/atool Latest version available: 0.39.0 Latest version installed: 0.39.0 Size of files: 116 kB Homepage: http://www.nongnu.org/atool/ Description: a script for managing file archives of various types License: GPL-2 * app-misc/screenfetch Latest version available: 9999 Latest version installed: 9999 Size of files: 0 kB Homepage: https://github.com/KittyKatt/screenFetch Description: A Bash Screenshot Information Tool License: GPL-3 * app-text/wgetpaste Latest version available: 2.25-r2 Latest version installed: 2.25-r2 Size of files: 10 kB Homepage: http://wgetpaste.zlin.dk/ Description: Command-line interface to various pastebins License: public-domain * net-analyzer/nbwmon Latest version available: 9999 Latest version installed: 9999 Size of files: 0 kB Homepage: https://github.com/causes-/nbwmon Description: ncurses bandwidth monitor License: MIT * media-sound/ncmpcpp Latest version available: 0.6_beta4 Latest version installed: 0.6_beta4 Size of files: 406 kB Homepage: http://ncmpcpp.rybczak.net/ Description: featureful ncurses based MPD client inspired by ncmpc License: GPL-2 * net-news/newsbeuter Latest version available: 2.8 Latest version installed: 2.8 Size of files: 421 kB Homepage: http://www.newsbeuter.org/index.html Description: A RSS/Atom feed reader for the text console License: MIT * sys-power/powertop Latest version available: 2.6 Latest version installed: 2.6 Size of files: 2,953 kB Homepage: https://01.org/powertop/ Description: tool that helps you find what software is using the most power License: GPL-2 Link to comment Share on other sites More sharing options...
haxmeister Posted October 2, 2014 Report Share Posted October 2, 2014 I think the following go without mention:irssi (IRC chat client) lynx (CLI web browser) htop (list most resource intensive running apps) Link to comment Share on other sites More sharing options...
666threesixes666 Posted October 2, 2014 Report Share Posted October 2, 2014 cowsay & fortune for your sexy command fortune | cowsay -d Link to comment Share on other sites More sharing options...
overkill Posted October 3, 2014 Report Share Posted October 3, 2014 for network info, 2 of my favorites: * net-analyzer/iftop Latest version available: 1.0_pre4 Latest version installed: 1.0_pre4 Size of files: 199 kB Homepage: http://www.ex-parrot.com/pdw/iftop/ Description: display bandwidth usage on an interface License: GPL-2 * net-analyzer/bmon Latest version available: 3.2 Latest version installed: 3.2 Size of files: 54 kB Homepage: http://www.infradead.org/~tgr/bmon/ Description: interface bandwidth monitor License: MIT and of course, * net-analyzer/mtr Latest version available: 0.85_p20140126 Latest version installed: 0.85_p20140126 Size of files: 218 kB Homepage: http://www.bitwizard.nl/mtr/ Description: My TraceRoute, an Excellent network diagnostic tool License: GPL-2 Link to comment Share on other sites More sharing options...
stac80 Posted October 3, 2014 Report Share Posted October 3, 2014 I've had an on again off again relationship with regularly monitoring my logfiles. I've used app-text/multitail which is good but I feel like there's probably something better out there that I'm not aware of. (By "better" I mean a log viewing program that is as simple or simpler than multitail. I don't monitor enough hosts to have some elaborate enterprise behemoth.) So do you guys generally monitor your logs in any way or do you use them when something goes wrong? I've done both and to be frank waiting until something stops working seems, for me, to take alot less "mental energy" than constantly having a terminal with log files spewing forth and that constant nag to want to check them. At the same time I catch little bugs and warnings, misconfigurations etc when regularly monitoring logs. I definitely feel more confident in the security and overall "health" of a more consistently monitored system. Where do you guys draw that line between consistent monitoring and checking logs retrospectively once something breaks? What tools do you use? (Don't limit yourselves to ebuilds. If you have trained a monkey or some other "offline" tool or trick to do this task I would be very interested in hearing about it.) Link to comment Share on other sites More sharing options...
haxmeister Posted October 4, 2014 Report Share Posted October 4, 2014 I monitor my logs retrospectively but I'm not functioning in a professional administrator capacity. I only administer funtoo on 2 desktops 1 server and 3 laptops in my home, for my family network. I suppose that a nifty python or Perl script running as a service could be written to watch logs and sort out messages that are not significant to you, posting those that are to CLI or other. Have you tried wtail ? I guess that's what multitail was based on? by the way.. which logs are you monitoring regularly? Link to comment Share on other sites More sharing options...
overkill Posted October 4, 2014 Report Share Posted October 4, 2014 I use logwatch for my logs, and pflogsumm for my postfix mail server logs. I run sysklogd for logging because at one time it was required for one of these utilities. It could have been required by both. I don't know if that is still the case or not. * sys-apps/logwatch Latest version available: 7.4.0_p170-r1 Latest version installed: 7.4.0_p170-r1 Size of files: 445 kB Homepage: http://www.logwatch.org/ Description: Analyzes and Reports on system logs License: MIT * net-mail/pflogsumm Latest version available: 1.1.5 Latest version installed: 1.1.5 Size of files: 46 kB Homepage: http://jimsun.linxnet.com/postfix_contrib.html Description: Pflogsumm is a log analyzer for Postfix logs License: GPL-2 Link to comment Share on other sites More sharing options...
Recommended Posts