Return-Path: Delivered-To: apmail-apache-bugdb-archive@apache.org Received: (qmail 92346 invoked by uid 500); 3 May 2000 20:18:16 -0000 Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: apache-bugdb@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-bugdb@apache.org Received: (qmail 92330 invoked by uid 501); 3 May 2000 20:18:15 -0000 Date: 3 May 2000 20:18:15 -0000 Message-ID: <20000503201815.92329.qmail@locus.apache.org> To: apache-bugdb@apache.org, bepeterson@taconic.net, coar@apache.org From: coar@apache.org Subject: Re: suexec/2075: suexec can't write log after failed exec & doesn't check execute permission [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ] Synopsis: suexec can't write log after failed exec & doesn't check execute permission State-Changed-From-To: feedback-closed State-Changed-By: coar State-Changed-When: Wed May 3 13:18:15 PDT 2000 State-Changed-Why: [This is a standard response.] No response from submitter, assuming issue has been resolved.