Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id VAA20574; Sun, 6 Jul 1997 21:31:09 -0700 (PDT) Received: from twinlark.arctic.org (twinlark.arctic.org [204.62.130.91]) by hyperreal.org (8.8.5/8.8.5) with SMTP id VAA20565 for ; Sun, 6 Jul 1997 21:31:06 -0700 (PDT) Received: (qmail 14952 invoked by uid 500); 7 Jul 1997 04:16:52 -0000 Date: Sun, 6 Jul 1997 21:16:52 -0700 (PDT) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: reliable piped logs In-Reply-To: <199707070424.XAA01086@sierra.zyzzyva.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Sun, 6 Jul 1997, Randy Terbush wrote: > Yes, I am working on the logging stuff. I backed off recently > trying to come up with a way to allow a syslog option to the > logging stuff. I know that there has been some skepticism about the > overhead of syslog for this, but I need to come up with some way > that load balanced servers could log to one place on the net. That > seems to be the logical solution. You're talking just about error logs right? At any rate, this would work: ErrorLog |logger -p local3.info -t httpd And you can use it when piped children are reliable :) Only problem is passing severities to syslog ... but that too could be done by a small perl script that talks apache log format (whatever that is!) and syslog format. Dean