site.authent — Another Example
site.authent
is set up with two
virtual hosts, one for customers and one for salespeople, and each
has its own logs in ... /logs/customers and
... /logs/salesmen. We can follow that scheme
and apply one LogFormat
to both, or each can have
its own logs with its own LogFormat
s inside the
<VirtualHost>
directives. They can also have
common log files, set up by moving ErrorLog
and
TransferLog
outside the
<VirtualHost>
sections, with different
LogFormat
s within the sections to distinguish the
entries. In this last case, the LogFormat
files
could look like this:
<VirtualHost www.butterthlies.com> LogFormat "Customer:..." ... </VirtualHost> <VirtualHost sales.butterthlies.com> LogFormat "Sales:..." ... </VirtualHost>
Let’s experiment with a format for customers, leaving everything else the same:
<VirtualHost www.butterthlies.com> LogFormat "customers: host %h, logname %l, user %u, time %t, request %r status %s, bytes %b," ...
We have inserted the words host
,
logname
, and so on
to make it clear in the file what is doing what. In real life you
probably wouldn’t want to clutter the file up in
this way because you would look at it regularly and remember what was
what or, more likely, process the logs with a program that would know
the format. Logging on to www.butterthlies.com
and going to summer
catalog
produces this log file:
customers: host 192.168.123.1, logname unknown, user -, time [07/Nov/ 1996:14:28:46 +0000], request GET / HTTP/1.0, status 200,bytes ...
Get Apache: The Definitive Guide, 3rd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.