swatch (the “Simple WATCHer”) does. swatch, written 100% in Perl, monitors logs as they're being written to and takes action when it finds something you've told it to look for. This simple, flexible and useful tool is a must-have for any healthily fearful system administrator.
"For a while now, IBM has had multiple and competing tools for managing AIX and Linux clusters for its supercomputer customers and yet another set of tools that were used for other HPC setups with a slightly more commercial bent to them. But Big Blue has now cleaned house, killing off its closed-source Cluster Systems Management (CSM) tool and tapping its own open source Extreme Cluster Administration Toolkit (known as xCAT) as its replacement."
"How to set up for usage with yum (minimum required version: yum 2.4.x): RHEL5, CentOS, Scientific Linux, RHEL4 yum, SLES yum Note: The version of yum distributed on CentOS 3 by default is too old (yum 2.0.8). You will need to upgrade to a yum 2.4.x version in order to use these repositories. The older version of yum does not support plugins or mirrorlists, which are required for these repos to work. "
"Linux Explorer ( LINUXexplo ) is a script that collects software and hardware information about a linux server for support purposes, similar to the Solaris explorer ( SUNWexplo ) , Redhat's "sysreport" and SuSE's "siga" script. The script is designed to collect information about a server to help service departments support linux and have a common set of scripts for collecting information about linux no matter what distro users are using. The information is stored in seperated directories, once all the information has been collected it then tar's up those directories into a single gzip tar file which can then be attached to an email for your support organization or copied to a remote server for safe keeping. "
Need to monitor Linux server performance? Try these built-in command and a few add-on tools. Most Linux distributions are equipped with tons of monitoring. These tools provide metrics which can be used to get information about system activities. You can use these tools to find the possible causes of a performance problem. The commands discussed below are some of the most basic commands when it comes to system analysis and debugging server issues such as: Finding out bottlenecks. Disk (storage) bottlenecks. CPU and memory bottlenecks. Network bottlenecks.