httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ondrej Sury <ond...@sury.org>
Subject Re: [PATCH] Re: Pluggable mod_log_config
Date Tue, 04 Oct 2005 12:59:40 GMT
On Mon, 2005-10-03 at 23:28 +0100, Colm MacCarthaigh wrote:
> And after all of this, what if any, are the compelling reasons to
> implement this in httpd at all? Why can't all of this be moved into
> piped loggers? Why can't they just parse the logs as they get them and
> do whatever whoever wants with it after that? After all, many people use
> "logger" to log to syslog. The whole mod_log_spread architecture with
> two netcat commands, and that can even be done with privilege
> seperation, which an in-httpd module never could.

No, it cannot be implemented with two netcat commands (just tried it).

Purpose of mod_log_spread is to unify several balanced frontends logging
to one common log server.  With netcat you can only do one to one.

Second problem that restart of backend server listener cannot cause
piped loggers to fail (and thus force you to restart all frontends).
Which is f.e. true for netcat.

Ondrej.
-- 
Ondrej Sury <ondrej@sury.org>

Mime
View raw message