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", >From IDG Books, Copyright 1998. The Sun Cobalt RaQs, by default, use one httpd.conf file. As far as I'm concerned, they've made the right decision. However, something runs in the RaQ that breaks up the single file into multiple files, which (on standard RaQs, possibly not on yours) are found at /home/sites/site*/logs/web.log/ This is what I couldn't find. I've just found it (spent over an hour on it); it happens as part of logrotate, which is in cron.daily. Specifically (for the archives <smile>) logrotate.conf points to a directory called /etc/logrotate.d, which includes the file "apache" which controls the running of /usr/local/sbin/split_logs. > If you post the contents of your httpd.conf then maybe we could see whether > there was a problem in that. Alternatively send it to me privately and I > will look at it for you. I'd rather not post it or send it; as you can imagine there might be some security holes in it. But I don't think you need it anymore; I believe I've found what I need to know. > Another possibility is that - if you manually were to delete a Apache log > file, then you must re-start Apache in order for it to continue writing a > new file with the same name. To further clarify... If you manually delete any file without restarting whatever is writing to it what happens is that the directory entry is deleted and the space is no longer reserved and becomes available for the creation of new files, BUT the program writing to it is NOT notified and continues to write to the same space. Thanks for your effort in helping me; your response helped me realize I'd have to do the research myself <smile>. Jeff -- Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA 92517 US Internet & Unix/Linux/Sun/Cobalt Consulting +1 909 778-9980 Our jblists address used on lists is for list email only To contact us offlist: "http://www.nobaloney.net/contactus.html"; _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
