[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] splitting logs...
- Subject: Re: [cobalt-developers] splitting logs...
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Sat Jan 4 16:42:01 2003
- Organization: nobaloney.net
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
Widebore Communications wrote:
> It is the /etc/httpd/conf/httpd.conf file which specifies if & where the
> Apache server is to write log files. By default the logs for all the virtual
> sites are stored as one big log file which Webalizer can analyse according
> to the site.
This is NOT what either any of the webalizer packages for the RaQs do,
nor is it what the custom installations by Cobalt do. In fact I don't
see, from reading the webalizer man file and the webalizer source code,
that webalizer can do this at all.
> But on my server I have changed the httpd.conf file so that the
> log file for each domain is stored in it's own folder e.g.
> /home/sites/www.site.com/logs/log as this makes it easier for me to handle
> each sites' logs/Webalizer data.
<aside>
RFC 2606 says we shouldn't use "site.com" as an example site, because
there reallyl is a site.com, and someone could accidentally refer to it,
not realizing your example is just an example. The proper use is
"example.com", which domain name is owned by IANA (The Internet Assigned
Numbers Authority) for the specific purpose of being used in examples.
This usage is described in RFC 2606 section 3 (see:
ftp://ftp.isi.edu/in-notes/rfc2606.txt.)
</aside>
There are some very good reasons to install a single logfile on a busy
webserver, having to do with how many file descriptors (file handles) a
process can use. You can read about this issue in any good book on the
apache webserver; I found it on page 151 of "The Apache Server Bible",