From: Daniel Earl Poirier Date: Tue, 19 Oct 2010 15:12:26 +0000 (+0000) Subject: Add warning about using rotatelogs filename formats with not X-Git-Tag: 2.2.18~364 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5dcfe419b1c0eabc0c64f350d714f5cb5e4e4fcc;p=thirdparty%2Fapache%2Fhttpd.git Add warning about using rotatelogs filename formats with not enough granularity. PR46318. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1024264 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/programs/rotatelogs.xml b/docs/manual/programs/rotatelogs.xml index 365437774da..bdfb34bbd8d 100644 --- a/docs/manual/programs/rotatelogs.xml +++ b/docs/manual/programs/rotatelogs.xml @@ -64,7 +64,7 @@ causes problems from some automated logging tools).
logfile
-
The path plus basename of the logfile. If logfile +

The path plus basename of the logfile. If logfile includes any '%' characters, it is treated as a format string for strftime(3). Otherwise, the suffix .nnnnnnnnnn is automatically added and is the time in @@ -72,7 +72,17 @@ seconds. Both formats compute the start time from the beginning of the current period. For example, if a rotation time of 86400 is specified, the hour, minute, and second fields created from the strftime(3) format will all be zero, referring to the -beginning of the current 24-hour period (midnight).

+beginning of the current 24-hour period (midnight).

+

When using strftime(3) filename formatting, +be sure the log file format has enough granularity to produce +a different file name each time the logs are rotated. Otherwise +rotation will overwrite the same file instead of starting a new +one. For example, if logfile was +/var/logs/errorlog.%Y-%m-%d with log rotation at 5 +megabytes, but 5 megabytes was reached twice in the same day, the +same log file name would be produced and log rotation would keep +writing to the same file.

+
rotationtime