Red HatThis forum is for the discussion of Red Hat Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
A checklist like this really depends on the configuration and isn't something that a forum will help you much with. Any suggestions you do get may not be right for your particular situation and everything about maintaining a server is contextual within your business processes, best practices, and personal preference. The only hard and fast rule is perform updates regularly but what regularly is depends on how often you want to handle those updates and all that is involved with them.
[QUOTE=alunduil;4067791The only hard and fast rule is perform updates regularly
Even that is a matter of opinion. Some knowledgeable people think it best
to perform security updates, but otherwise follow "if it aint broke
don't fix it". Updates do occasionally cause problems, of course, so one
reasonable line of thought is that if the update doesn't provide anything
you need, it's best not to do the update and risk a problem.
There's actually not much that needs to be done on a regular basis, generally.
Those things that need to be done regularly are most often handled
automatically via cron. One thing that can bite you, though, is if
you don't have a cron job to truncate or rotate your logs. You'll want
to check that logrotate or something is being used to get rid of old logs.
Otherwise, you end up filling up your disk and things get nasty when the
drive is completely full. Check disk space 30,60, and 90 days after
deployment to make sure nothing is slowing filling it.
If you set a working email address for root in /etc/aliases, the automated
monitoring tools like logwatch will send you daily emails of things
that might be of interest, so you need not go check those things
regularly. For example, it will email you if a partition is getting
too full. You may want to filter those messages a bit by adjusting
logging options or whatever to get rid of the stuff you don't want to
see. That way you don't stop reading them and miss something important.
I am targeting installation of 'sysstat' package for my servers. However, I require some guidance on this for the following:
a) pre-requisites to be met.
b) step by step guide for installation, if any
RHE Linux site does not seem to give much information on the installation of this package. Please correct me if I am wrong.
That's the beauty of using Red hat and other distros with good package
managements systems. The pre-requisites and such are handled automatically.
yum install sysstat
Older Red hat versions don't have a new enough version of Python, as I
recall (or maybe that's for iostat). Lots of things depend on Python,
so that makes things difficult. I'm probably thinking of iostat, though.