Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3FA3CE7E.7030803@attglobal.net>
Date: Sat, 01 Nov 2003 10:17:18 -0500
From: Jeff Trawick <trawick@attglobal.net>
Reply-To: trawick@attglobal.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: piped log files
References: <6.0.0.22.2.20031101160426.031464f0@pop.web4friends.com>
In-Reply-To: <6.0.0.22.2.20031101160426.031464f0@pop.web4friends.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Bastiaan van der Put wrote:

> Piped log files still dont work with apache 2.0.48
> 
> piped log program '/usr/local/apache2/bin/logresolve >> 
> /home/accounts/x/xxxxxxxx/logs/access_log' failed unexpectedly
> 
> So i am using a script as suggested before , called it apacheresolve :
> 
> #!/bin/sh
> exec /usr/local/apache2/bin/logresolve >>/tmp/lr.out

I still have this patch in my tree for this feature.  ISTR wondering what other 
people thought about it, and forgetting about the issue until you just brought 
it up again.  Any concerns out there?

Index: server/log.c
===================================================================
RCS file: /home/cvs/httpd-2.0/server/log.c,v
retrieving revision 1.135
diff -u -r1.135 log.c
--- server/log.c        14 Jul 2003 14:48:40 -0000      1.135
+++ server/log.c        1 Nov 2003 15:13:35 -0000
@@ -743,6 +743,8 @@
      apr_status_t status;

      if (((status = apr_procattr_create(&procattr, pl->p)) != APR_SUCCESS) ||
+        ((status = apr_procattr_cmdtype_set(procattr, APR_SHELLCMD))
+         != APR_SUCCESS) ||
          ((status = apr_procattr_child_in_set(procattr,
                                               ap_piped_log_read_fd(pl),
                                               ap_piped_log_write_fd(pl)))

Any comments from the audience?

> When stopping apache I also get :
> 
> piped log program '/usr/local/apache2/bin/apacheresolve >> 
> /home/accounts/x/xxxxx/logs/access_log' failed unexpectedly

There is a PR for this issue.  It is perhaps timing related, as it does not 
affect everybody.