From: Jim Jagielski Date: Mon, 26 Nov 2007 13:52:03 +0000 (+0000) Subject: update docco xforms X-Git-Tag: 2.2.7~192 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7ff0650b2d1ed7212867f6cf02e107ddd51fed06;p=thirdparty%2Fapache%2Fhttpd.git update docco xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@598276 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/programs/rotatelogs.html.en b/docs/manual/programs/rotatelogs.html.en index 7d637a7400b..f20b3ef2751 100644 --- a/docs/manual/programs/rotatelogs.html.en +++ b/docs/manual/programs/rotatelogs.html.en @@ -23,36 +23,12 @@

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 -

- -

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 /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.

- + conjunction with Apache's piped logfile feature. It supports + rotation based on a time interval or maximum size of the log.

top
@@ -62,8 +38,8 @@

rotatelogs [ -l ] logfile - [ rotationtime [ offset ]] | - [ filesizeM ]

+ rotationtime|filesizeM + [ offset ]

top

Options

@@ -72,8 +48,10 @@
-l
Causes the use of local time rather than GMT as the base for the -interval. Note that using -l in an environment which changes the -GMT offset (such as for BST or DST) can lead to unpredictable results!
+interval or for 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!
logfile
@@ -82,24 +60,71 @@ 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 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).
rotationtime
-
The time between log file rotations in seconds.
+
The time between log file rotations in seconds. The rotation +occurs at the beginning of this interval. For example, if the +rotation time is 3600, the log file will be rotated at the beginning +of every hour; if the rotation time is 86400, the log file will be +rotated every night at midnight. (If no data is logged during an +interval, no file will be created.)
+ +
filesizeM
+ +
The maximum file size in megabytes followed by the letter +M to specify size rather than time.
offset
The number of minutes offset from UTC. If omitted, zero is assumed and UTC is used. For example, to use local time in the zone -UTC -5 hours, specify a value of -300 for this argument.
- -
filesizeM
+UTC -5 hours, specify a value of -300 for this argument. +In most cases, -l should be used instead of specifying +an offset. -
The maximum file size in megabytes followed by the letter -M to specify size rather than time. Use this parameter -in place of both rotationtime and offset.
+
top
+
+

Examples

+ +

+ 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.

+
top

Portability

diff --git a/docs/manual/programs/rotatelogs.xml.ko b/docs/manual/programs/rotatelogs.xml.ko index 053a8127c34..7dcf328c428 100644 --- a/docs/manual/programs/rotatelogs.xml.ko +++ b/docs/manual/programs/rotatelogs.xml.ko @@ -1,7 +1,7 @@ - +