Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Seems like a simple question, but I can't find an answer for it.
How does webalizer handle wildcards? For instance, my server runs webalizer on an hourly rotation and logrotate on a daily rotation. Can I get it to analyze both access_log and access_log.1 (the previous day's log) so that it doesn't miss any log entries from the previous hour before the rotation? For some reason there's nothing in the webalizer documentation on wildcards for the access log.
It would seem that it's not missing anything. The way my log rotation works is that it adds a numbered extension of the rotated log file (access_log, access_log.1, access_log.2). So it would seem that this line in my webalizer.conf:
Code:
LogFile /var/log/httpd/access_log
already acts like a wildcard by analyzing anything that begins with access_log. Would I be correct in that assumption?
Ok, so that is taking care of the log rotation. Every time webalizer runs, it puts data into that history file so that when you rotate the logs, it doesnt care that the old data is not there.
Let me put this another way... I'm running a server on Fedora Core 2. Still mostly a default setup. One of the excpetions being that I changed webalizer to an hourly rotation on the hour. The logroate script is in the daily folder, which runs at 4:02 AM (default scheduled time). So the hourly webalizer run would be two minutes before the log rotation is supposed to occur. How would I get it to not miss that last two minutes before the log was rotated?
Well, I guess you could create a second webalizer script that will run after the log rotate and look at the file access_log.1, or whatever the file is that the file gets renamed to. Other than that I dont think that there is an automatic way to do it.
That's an idea. Thanks, hadn't thought about doing that. I gathered that running them at the same time probably wouldn't be a good idea due to file locks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.