From: Jim Jagielski This creates the files /var/logs/logfile.nnnn where nnnn is
- the system time at which the log nominally starts (this time
- will always be a multiple of the rotation time, so you can
- synchronize cron scripts with it). At the end of each rotation
- time (here after 24 hours) a new log is started. This configuration will rotate the logfile whenever it reaches
- a size of 5 megabytes. This configuration will rotate the error logfile whenever it
- reaches a size of 5 megabytes, and the suffix to the logfile name
- will be created of the form
- rotatelogs is a simple program for use in
- conjunction with Apache's piped logfile feature. For example:
- CustomLog "|bin/rotatelogs /var/logs/logfile 86400" common
-
- CustomLog "|bin/rotatelogs /var/logs/logfile 5M" common
-
- ErrorLog "|bin/rotatelogs /var/logs/errorlog.%Y-%m-%d-%H_%M_%S 5M"
-errorlog.YYYY-mm-dd-HH_MM_SS.
rotatelogs
[ -l ]
logfile
- [ rotationtime [ offset ]] |
- [ filesizeM ]
-l-l in an environment which changes the
-GMT offset (such as for BST or DST) can lead to unpredictable results!strftime(3) formatting with size-based
+rotation. Note that using -l in an environment which
+changes the GMT offset (such as for BST or DST) can lead to unpredictable
+results!
logfilestrftime(3). Otherwise, the suffix
.nnnnnnnnnn is automatically added and is the time in
seconds. Both formats compute the start time from the beginning of
-the current period.
+the current period. For example, if a rotation time of 86400 is
+specified, the hour, minute, and second fields created by
+strftime(3) format will all be zero, referring to the
+beginning of the current 24-hour period (midnight).
rotationtimefilesizeMM to specify size rather than time.offset-300 for this argument.filesizeM-300 for this argument.
+In most cases, -l should be used instead of specifying
+an offset.
-M to specify size rather than time. Use this parameter
-in place of both rotationtime and offset.
+ CustomLog "|bin/rotatelogs /var/logs/logfile 86400" common
+
This creates the files /var/logs/logfile.nnnn where nnnn is + the system time at which the log nominally starts (this time + will always be a multiple of the rotation time, so you can + synchronize cron scripts with it). At the end of each rotation + time (here after 24 hours) a new log is started.
+ +
+ CustomLog "|bin/rotatelogs -l /var/logs/logfile.%Y.%m.%d 86400" common
+
This creates the files /var/logs/logfile.yyyy.mm.dd where + yyyy is the year, mm is the month, and dd is the day of the month. + Logging will switch to a new file every day at midnight, local time.
+ +
+ CustomLog "|bin/rotatelogs /var/logs/logfile 5M" common
+
This configuration will rotate the logfile whenever it reaches + a size of 5 megabytes.
+ +
+ ErrorLog "|bin/rotatelogs /var/logs/errorlog.%Y-%m-%d-%H_%M_%S 5M"
+
This configuration will rotate the error logfile whenever it
+ reaches a size of 5 megabytes, and the suffix to the logfile name
+ will be created of the form
+ errorlog.YYYY-mm-dd-HH_MM_SS.