Re: Logging extensions to NCSA httpd 1.3

["Robert S. Thau" <rs...@ai.mit.edu>]

   From: dlincke@bandon.unisg.ch (David-Michael Lincke)
   Date: 27 Feb 95 22:59:35 

   The following new configuration directives are available:

	   * RefererLog <filespec>
	   * RefererExclude <pattern>
	   * UaLog <filespec>

Just a brief comment on this patch --- I've wanted to see this info
myself, but my personal preference would be to fold these fields,
at least optionally, into the existing access_log.  (Of course, part
of that comes from knowing that neither of the log file analysers I
use, wwwstat or my own local Perl script, will be especially bothered
by new fields at the end of access_log lines).

Believe it or not, the cost of writing log files isn't entirely
trivial (it amounts to about 5-7% of the CPU time on my most recent
profiles, which exclude fork() overhead, but include most everything
else --- most of that time is write() and close()).  I'm not griping
about 5%, but I wouldn't want it getting much worse, and having two
new, entirely separate files could do that.

rst

Re: Logging extensions to NCSA httpd 1.3

[Brian Behlendorf <br...@wired.com>]

On Tue, 28 Feb 1995, Robert S. Thau wrote:
> Just a brief comment on this patch --- I've wanted to see this info
> myself, but my personal preference would be to fold these fields,
> at least optionally, into the existing access_log.  (Of course, part
> of that comes from knowing that neither of the log file analysers I
> use, wwwstat or my own local Perl script, will be especially bothered
> by new fields at the end of access_log lines).

My opinion is that so much of the information is redundant that the 
logging only really needs to take place on a couple of places in a given 
web tree.  I have a script on the HW subscriber home page launched via 
a server-side include for this purpose... I guess as long as it's 
optional I can always turn it off.

	Brian


--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@hotwired.com  brian@hyperreal.com  http://www.hotwired.com/Staff/brian/