Re: mod_cgi/4115: CGI Execs properly from ScriptAlias Directory, Error 500 anywhere else. (fwd)

[Marc Slemko <ma...@znep.com>]

The following reply was made to PR mod_cgi/4115; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: Apache bugs database <ap...@apache.org>
Cc:  Subject: Re: mod_cgi/4115: CGI Execs properly from ScriptAlias Directory,
 Error 500 anywhere else. (fwd)
Date: Sun, 28 Mar 1999 15:07:20 -0800 (PST)

 ---------- Forwarded message ----------
 Date: Wed, 24 Mar 1999 17:06:55 -0500
 From: Kutulu <ku...@cyber-wizard.com>
 To: apache-bugdb@apache.org, marc@apache.org
 Subject: Re: mod_cgi/4115: CGI Execs properly from ScriptAlias Directory,
      Error 500 anywhere else.
 
 Ack!  You're absolutely right.
 
 The web server is running as 'nobody' (the default from httpd.conf), but the
 suexec caller is set to 'www' (the default from suexec.h.  I just recompiled
 with --suexec-caller=nobody, now it works like a champ.  Sorry to bug you
 for something so simple :(
 
 --Kutulu
 
 ----- Original Message -----
 From: <ma...@apache.org>
 To: <ap...@apache.org>; <ku...@cyber-wizard.com>; <ma...@apache.org>
 Sent: Wednesday, March 24, 1999 4:43 PM
 Subject: Re: mod_cgi/4115: CGI Execs properly from ScriptAlias Directory,
 Error 500 anywhere else.
 
 
 > [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!         ]
 >
 >
 > Synopsis: CGI Execs properly from ScriptAlias Directory, Error 500
 anywhere else.
 >
 > State-Changed-From-To: open-feedback
 > State-Changed-By: marc
 > State-Changed-When: Wed Mar 24 13:43:30 PST 1999
 > State-Changed-Why:
 > Do you have suexec enabled?
 >
 > Is anything printed about "suexec" in the error log when you start Apache?
 >
 > If you do have suexec enabled, did you look in the suexec
 > cgi.log?
 >