From: Eric Covener Date: Wed, 13 May 2020 20:44:42 +0000 (+0000) Subject: mention relative path behavior, offline question X-Git-Tag: 2.5.0-alpha2-ci-test-only~1439 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=010d3aa68a9e1957f6febbba3dec22fd0bddc0db;p=thirdparty%2Fapache%2Fhttpd.git mention relative path behavior, offline question git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1877708 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/programs/rotatelogs.xml b/docs/manual/programs/rotatelogs.xml index 581e2e76ef9..3ecc3ce22cf 100644 --- a/docs/manual/programs/rotatelogs.xml +++ b/docs/manual/programs/rotatelogs.xml @@ -59,10 +59,16 @@ interval or for strftime(3) formatting with size-based rotation.
-L linkname
-
Causes a hard link to be made from the current logfile +

Causes a hard link to be made from the current logfile to the specified link name. This can be used to watch the log continuously across rotations using a command like -tail -F linkname.

+tail -F linkname.

+

If the linkname is not an absolute +path, it is relative to rotatelogs' working directory, +which is the ServerRoot when +rotatelogs is run by the server. +

+
-p program
@@ -137,6 +143,11 @@ one. For example, if logfile was 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.

+

If the logfile is not an absolute +path, it is relative to rotatelogs' working directory, +which is the ServerRoot when +rotatelogs is run by the server. +

rotationtime