httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Slive <>
Subject Re: Parsing Log Files
Date Wed, 01 May 2002 14:14:47 GMT

On Wed, 1 May 2002, RichardH wrote:
> Second post (me):
> The only problem with using the transferlog directive, is that for each an
> every virtual host entry that is used in the manner, you have another open
> file process. In time this will overload your server and create server slow
> down.
> By parsing out the files with a script, it reduces overall server load AND
> permits the use of rewrite rules, that allow you to use a virtmap.txt type
> of setup for hosting entries (in which case the transferlog entry does not
> work at all).
> The transferlog directive is fine for a small production server, where you
> are hosting a few accounts, but for a large application, is not such a wise
> idea.


The only trick if you are using a non-standard virtual hosting technique
is to get apache to put something unique into the logfile for each vhost.
This isn't normally too difficult, because the logging is very flexible.
Then you use a script like split-logfile (modified by you as appropriate)
to do the splitting.

Note that if you allow a root process (including the apache logging
process) to write to a non-root owned directory (or a child of a non-root
owned directory) you are opening a huge security hole.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message