glim wrote:
Greetings. If this isn't being sent to the correct list, I apologize.
Let me know and I'll go elsewhere.
I'd like to make a minor improvement to rotatelogs and wanted to check
with the list to see what would be most appreciated.
"rotatelogs" as it stands now cannot rotate by time and date in a single
invocation.
I'm willing to write a patch to do this, but as I said, I'd like to find
out what would best suit the community.
The problem: For log analysis, we'd like the day-of-the-year to be
contained in the name of the logfile. IOW any given logfile should only
contain logs for events happening during that day. We would also at the
same time, like to insure that logs do not grow larger than 500M.
Rotatelogs accepts a single parameter to specify a condition for
rotation. You can select size XOR time-based rotation - not both. You
can see why from the current syntax:
rotatelogs [-l] [-f] <logfile> {<rotation time in seconds>|<rotation
size in megabytes>} [offset minutes from UTC]
I'd propose something more like this:
%s [-l] [-f] [-s=rotation-size-in-megabytes]
[-t=rotation-time-in-seconds [-o=offset-minutes-from-UTC]] <logfile>
Here are some options:
1. new syntax - pro: upgrade all options to use apr_getopt(), simple
syntax, relatively small patch to rotatelogs. con: requiring flags for
options will break unprepared users.
I'd vote for doing this on trunk, 2.2.x backport can be skipped or
rethought once we have it working.
-Paul
