Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 62998 invoked from network); 21 Aug 2007 11:37:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Aug 2007 11:37:59 -0000 Received: (qmail 62963 invoked by uid 500); 21 Aug 2007 11:37:49 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 62879 invoked by uid 500); 21 Aug 2007 11:37:49 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 62868 invoked by uid 99); 21 Aug 2007 11:37:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 04:37:49 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [194.242.35.95] (HELO dns-factory.at) (194.242.35.95) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 11:38:19 +0000 Received: from WSLT03 apache@gknw.net [84.63.52.14] by dns-factory.at with NetMail SMTP Agent $Revision: 6820 $ on Novell NetWare; Wed, 22 Aug 2007 01:36:14 +0200 Date: Tue, 21 Aug 2007 13:37:24 +0200 From: Guenter Knauf To: dev@httpd.apache.org Subject: Re: And 2.2.6 Re: Notice of Intent: T&R 2.0.61 Message-ID: <4PXicVarr9ySsxjtMfXdXeLDTusH3Gy9Lmz3F1kUzPM@akmail> References: <135260DB-35BD-42E5-BA54-AB24063B9CF4@jaguNET.com> <46C9FB6B.8020207@rowe-clan.net> <20070820210057.GB25384@redhat.com> X-Mailer: AK-Mail 4.01 [German] (registered, single user license) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi, > The fact that the apr_proc* API is so horribly convoluted yet still > broken on Win32 is kind of ironic. If it's not fixable can we just > abandon it? The code to implement piped loggers can be much simpler and > more efficient on Unix if implemented natively. may I ask a question on this topic:=20 why is piped logging so important, and why dont we add f.e. mod_log_rotate= which does the job of rotating logs more nicerly on every platform? That = would avoid 95% usage of piped logging: http://www.hexten.net/wiki/index.php/Mod-log-rotate sure, maybe there are other implementations like mysqllog or pgsqllog, and= such which use piped logging; however I've tried already a lot, and none = of all these 'solutions' work really reliable... Guen.