Re: Apache logging and fifo's

On Fri, Jun 25, 2004 at 07:26:49PM -0700, Glenn Willen wrote:
>Quoting George Georgalis <[email protected]>:
>> I did a lot of experimentation with apache/multilog. I ended up using
>> apache logging for access and multilog for error
>
>Am I correct in recalling that there is a non-backgrounding patch for apache?
>Because my absolute instinctive first thought is just to patch apache so it can
>log to /dev/fd/1 and 2, and use it with multilog as djb intended. :-) I tried
>naively telling apache in its config file to log to /dev/fd/1, but of course
>that's opened as /dev/null so that goes to the bitbucket... but I was thinking
>that a non-backgrounding patch would probably leave fd1/2 open to the terminal,
>right? So, could it work? Or am I crazy?

There is a foreground switch, -F I use it to run apache under svcscan,
but you don't want logging to stdout/err. apache is designed to manage
children and each child would have it's own stdout if you try logging
that way.

There's a configuration option, ServerType (so you could run it under
tcpserver and use stdout/err) If you use tcpserver you'll see a big
performance hit because each connection will need to load up a new
instance and you won't have the apache standby servers feature.

// George


-- 
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/  cell:646-331-2027  mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7  9EF0 0186 503B 9831 1631