Received: (qmail 31174 invoked by uid 501); 12 Dec 2000 13:52:52 -0000
Message-Id: <20001212135252.31173.qmail@locus.apache.org>
Date: 12 Dec 2000 13:52:52 -0000
From: Glennan Carnie <carnieg@uk.ibm.com>
Reply-To: carnieg@uk.ibm.com
To: submit@bugz.apache.org
Subject: TransferLog ignores LogFormat directives
X-Send-Pr-Version: 3.110

>Number:         6965
>Category:       general
>Synopsis:       TransferLog ignores LogFormat directives
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Dec 12 06:00:02 PST 2000
>Closed-Date:    Tue Dec 12 10:52:21 PST 2000
>Last-Modified:  Tue Dec 12 10:52:21 PST 2000
>Originator:     carnieg@uk.ibm.com
>Release:        1.3.12
>Organization:
>Environment:
AIX 4.3.3
>Description:
We are using TransferLogs (as recommended) to rotate our logs daily, using rotatelogs.
Our httpd.conf file is set as follows (excerpt only):

# Log rotation:
# Rotate the logs every 24 hours.
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" \"%{cookie}ni\"" combined

TransferLog "|/usr/HTTPServer/bin/rotatelogs /usr/HTTPServer/logs/access_log 86400"

According to the online documentation, the TransferLog directive should use the last defined LogFormat directive (in our case, the one directly preceding it).  However, the TransferLog directive seems to ignore the LogFormat and always produces a log using the (default) Common format.

Note: the formatting works just fine with the CustomLog directive.

These symptoms occur whether rotatelogs is used, or another log rotation utility such as Cronolog.


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: slive
State-Changed-When: Tue Dec 12 10:52:19 PST 2000
State-Changed-Why:

Please see the docs for LogFormat, which tell you that
there are two syntaxes of this directive.  When
Logformat is specified with one argument, it defines
the format for future TransferLog directives.  When
it is specified with two arguments (as you have done)
it ONLY defines a nickname, and does not change the
TransferLog.

As an alternative, you can use CustomLog which can accept
the nickname defined by LogFormat.

Thanks for using Apache!
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]