Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is my first post, I searched on 'log rotation', 'webalizer', 'cronolog' and got a mixture of forums - so apologies if this is the wrong place.
I am running Apache 2 on RH ES (no load balancing or clustering), running multiple virtual hosts (each with their own log files). I am rotating these log files weekly using Cronolog (%Y_<vitrtualhostname>_access.log.%W) and have setup Webalizer conf files for each of these.
How I was planning to do it was to use Cronolog's -S and -P switches to have a '.thisweek' and '.lastweek' access files with Webalizer's config set to read .lastweek. I can then archive older log files later in the week.
However, Apache does go through any number of graceful restarts during the week (mainly because mod_perl2's object reload doesn't seem to be working 100% as desired). I think that the Apache restart causes
.lastweek to link the same file as .thisweek (Cronolog seems to get confused).
The restarts are, realistically, unavoidable.
Any suggestions on a different way to achieve my goal (or a way to fix the above)?
The aim is to produce stats weekly, rotate regularly (preferably weekly) and archive at least monthly (or 4 weekly, whatever). I'm finding it difficult to come up with a good strategy across the 3 requirements (rotate, analyse, archive) that is reliable.