suexec/2765: Suexec Reporting

[Andrew Petrie <ni...@wantree.com.au>]

>Number:         2765
>Category:       suexec
>Synopsis:       Suexec Reporting
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Aug  2 22:30:01 PDT 1998
>Last-Modified:
>Originator:     nitro@wantree.com.au
>Organization:
apache
>Release:        1.3.1
>Environment:
Linux 2.0.35 (i386), gcc 2.7.2.3
>Description:
I have seen the previous bug reports on suexec reporting. The error
log DOES NOT show suexec running, nor does the access log. The server
starts up, and appears to be using suexec (it creates a cgi.log as defined
in suexec.h, and an strace of httpd shows it successfully stating it), but
it does not report this anywhere.
>How-To-Repeat:
I have tried many different configurations of apache, from fresh clean installs
on machines that haven't had apache on them, to upgraded 1.2 servers, with
1.2 style heirachy - All of them do it.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]