httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [PATCH] Disabling logging based on envariable
Date Sat, 16 Aug 1997 02:50:08 GMT
I too prefer the unix trend.  But that's not what we're headed for at the
moment ... not this patch in particular, just in general.  We have special
case directives left and right.  It's not something we'll solve in 1.3
though ... my "huge throbbing diseased bags" grow horizontally, yours grow
vertically.  Not much difference.  I'm not going to fight for my way
though, because I'm pretty sure we've already agreed that 2.0 can include
a config language revamp. 

By "vertical" I'm referring to distinct directives which interrelate with
each other, modifying the same "object".  (In your case modifying a
"logging object".)  Horizontal is when a single directive (modifying a
single object) has its configurability extended.

Anyhow, that all said and done.... if anyone recalls, the last time this
whole log configurability issue came up I said "why don't we make piped
logs reliable and then people can write perl scripts to do whatever the
hell they want?".  And I just haven't had the time to finish it up :( If
someone wants to take the register_other_child api I posted recently and
finish the work, please tell me!  You've got to get it done in the next
two weeks though ;)

Dean

On Fri, 15 Aug 1997, Rodent of Unusual Size wrote:

> >From the fingers of Dean Gaudet flowed the following:
> >
> >Rob's example, and Ken's both add directives.  As usual I disagree with
> >that :)  My suggestion:
> >
> >CustomLog logs/kaboom "%h - %u %t \"%r\" %s %b" !that_bloody_robot_again
> >
> >That is, CustomLog takes a log filename, a log format string, and an
> >optional environment variable that must be present (or not present).  This
> >isn't a lot more work.
> 
>     I dislike it.  Strongly.  (Possibly because I had already started
>     working on Rob's suggestion.)  I disagree thoroughly with this
>     tendency to hang huge throbbing diseased bags on the sides of existing
>     directives.  We went through this to some extent with the Mumble
>     versus MumbleMatch discussion a few weeks ago.
> 
>     The CustomLog directive is already cryptic enough with the format
>     string.  We're keeping the directives text-based, but making them
>     harder to read & use (IMHO).  This is the wrong trend.  I prefer the
>     UNIX model of having little limited-function pieces that can work
>     together.
> 
>     #ken    :-(}
> 


Mime
View raw message