Re: log to multilog instead of file

On Thu, May 27, 2004 at 11:43:48AM -0400, Paul Jarc wrote:
> richard lucassen <[email protected]> wrote:
[snip]
> > I think the use of /dev/stderr is a more elegant solution then
> > the (mis)use of a fifo.
> 
> More reliable, too.  With a fifo, if the reader and writer both happen
> to die, and there is data left in the pipe, that data will be lost.
> svscan keeps the *same* pipe for the restarted processes to use, so no
> data is lost, as long as the reader gets back on its feet eventually.

On a related note, since I too am using fifos with multilog, what happens if I'm running something like, say, apache-ssl?  It just so happens to have not one but three logs:

ErrorLog /var/log/apache-ssl/chroot/error.fifo
CustomLog /var/log/apache-ssl/chroot/combined.fifo combined
CustomLog       /var/log/apache-ssl/chroot/ssl.fifo "%{version}c %{cipher}c %{clientcert}c"

I could, obviously, get only one custom log, but I'd still have two logs total.  Can I have both writing to /dev/stderr?  Or is that a "bad" idea.  Right now, I simply have three "extra" services which handle listening to the log fifos, and then the actual apache service like so:

/service $ ls |grep apache
apache-ssl-combined_log
apache-ssl-error_log
apache-ssl-ssl_log
apache-ssl

I have a similar setup with squid, which also has three separate "logs," (namely access, cache, and store), in addition to the daemon writing to the pipe to multilog already.

thanks!

-- 
adam