Multiple log files
Bug #611450 reported by
mjulius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| AWFFull |
New
|
Undecided
|
Unassigned | ||
Bug Description
On servers where the log files are rotated frequently it is likely that they are rotated between two awffull runs. To catch all log entries awffull needs to scan both the first rotated and the current log file.
In Debian's cron job this is currently achieved by examining the config file and if the LogFile specified in there looks like a rotated one awffull is run again with the current log file. This is ugly. And this causes awffull to behave differently depending on whether it is called directly or from the cron job which might be confusing to some people.
This issue could be resolved nicely if several log files could be specified in the config or on the command line which would be scanned in the order they appear.
Revision history for this message
| Steve McInerney (spm) wrote | #1 |
To post a comment you must log in.
Fair enough. Usually the 'better' way to solve this as it currently stands is to bunch the logs needed in appropriate shell and pipe into awffull.
eg. If you're rotating multiple times a day, the sensible trick would be to date+time stamp the logs, so a single glob could catch the lot:
zcat logs.2010-08-01*.gz | awffull ...
Or as part of the rotation, spawn off an awfull run on the newly rotated logfile.
But yeah, being able to process > 1 log on the cmd line in particular would be good.
Issues around appropriate merging of time info, so the order of logs didn't matter; so not as simple as we may like unf.