From owner-freebsd-isp Tue May 18 8:46:32 1999 Delivered-To: freebsd-isp@freebsd.org Received: from kiwi.datasys.net (kiwi.hefty.org [209.119.145.2]) by hub.freebsd.org (Postfix) with ESMTP id A832B15064 for ; Tue, 18 May 1999 08:46:00 -0700 (PDT) (envelope-from ayan@kiwi.datasys.net) Received: (from ayan@localhost) by kiwi.datasys.net (8.9.3/8.9.3) id LAA02511 for freebsd-isp@FreeBSD.ORG; Tue, 18 May 1999 11:45:57 -0400 (EDT) (envelope-from ayan) Date: Tue, 18 May 1999 11:45:57 -0400 (EDT) From: Ayan George Message-Id: <199905181545.LAA02511@kiwi.datasys.net> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-isp@FreeBSD.ORG Subject: Re: Apache log files Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wonder how much of a perormance impact forking logger would have vs. using syslog(), especially on high traffic servers. [ Quoted message from Matthias Meyser, recieved May 18, 5:34pm.] > Why hacking apache? Instead of specifying a file to log to in the > apache.conf you can also specify a command to pipe the entries to. > > What about piping to "logger"? > [ End message from Matthias Meyser. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message