DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9038>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9038
suexec is NOT being called by Apache 2.0.36
Summary: suexec is NOT being called by Apache 2.0.36
Product: Apache httpd-2.0
Version: 2.0.36
Platform: PC
OS/Version: FreeBSD
Status: NEW
Severity: Major
Priority: Other
Component: mod_suexec
AssignedTo: bugs@httpd.apache.org
ReportedBy: abatko@cs.mcgill.ca
suexec is NOT being called by Apache 2.0.36.
I've built apache both from /usr/ports on FreeBSD (4.5-RELEASE-p4)
and from the latest source downloaded from the apache website.
In both cases, upon start of apache, the following notice arrives
in apache's error logfile, indicating that suexec has been loaded:
[notice] suEXEC mechanism enabled (wrapper: /usr/local/sbin)
However in both cases, the suexec logfile is never modified.
Just to try figure out what's going on,
I modified suexec's main() function by adding the following
function call to send a message to suexec's logfile:
log_err("testing... entered suexec\n");
This message never arrives when a cgi script is called; however
it does arrive if suexec is called manually from the shell.
I have also temporarily replaced the suexec program with the
following shell script to see if there would be any difference:
#!/bin/sh
DATE=`/bin/date`
cat >> /tmp/fake_suexec << EOF
$DATE
$*
EOF
Again, when a cgi script is called from a web browser, suexec is
not executed because in this case, /tmp/fake_suexec is not modified.
On the other hand, when this shell script is executed from the
command line, it of course works.
The compiled-in modules are:
core.c
prefork.c
http_core.c
mod_so.c
And the additional loaded modules are:
mod_access.so
mod_alias.so
mod_autoindex.so
mod_cgi.so
mod_cgid.so
mod_dir.so
mod_include.so
mod_log_config.so
mod_mime.so
mod_negotiation.so
mod_setenvif.so
mod_status.so
mod_suexec.so
mod_userdir.so
The suexec-related bugs i found in the apache bug database are
not related to what i'm reporting:
7810 suexec + userdir non-functional in httpd 2.0.35
7992 Core dump when restarting daemon with mod_suexec
8291 mod_include + mod_suexec has bug
7862 suexec never log a group name
7791 mod_suexec problem
8789 SuExec Log File does not get created by default when suexec
Running apache with 'LogLevel debug' did not reveal anything insightful.
I have no idea where to even begin looking through the apache source
code to try to resolve this problem, so i'm wondering if someone else
can please take a look. If you need any more information, please let
me know. Thank you very much for you time, and for the Apache server!!!
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9038>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9038
suexec is NOT being called by Apache 2.0.36
Summary: suexec is NOT being called by Apache 2.0.36
Product: Apache httpd-2.0
Version: 2.0.36
Platform: PC
OS/Version: FreeBSD
Status: NEW
Severity: Major
Priority: Other
Component: mod_suexec
AssignedTo: bugs@httpd.apache.org
ReportedBy: abatko@cs.mcgill.ca
suexec is NOT being called by Apache 2.0.36.
I've built apache both from /usr/ports on FreeBSD (4.5-RELEASE-p4)
and from the latest source downloaded from the apache website.
In both cases, upon start of apache, the following notice arrives
in apache's error logfile, indicating that suexec has been loaded:
[notice] suEXEC mechanism enabled (wrapper: /usr/local/sbin)
However in both cases, the suexec logfile is never modified.
Just to try figure out what's going on,
I modified suexec's main() function by adding the following
function call to send a message to suexec's logfile:
log_err("testing... entered suexec\n");
This message never arrives when a cgi script is called; however
it does arrive if suexec is called manually from the shell.
I have also temporarily replaced the suexec program with the
following shell script to see if there would be any difference:
#!/bin/sh
DATE=`/bin/date`
cat >> /tmp/fake_suexec << EOF
$DATE
$*
EOF
Again, when a cgi script is called from a web browser, suexec is
not executed because in this case, /tmp/fake_suexec is not modified.
On the other hand, when this shell script is executed from the
command line, it of course works.
The compiled-in modules are:
core.c
prefork.c
http_core.c
mod_so.c
And the additional loaded modules are:
mod_access.so
mod_alias.so
mod_autoindex.so
mod_cgi.so
mod_cgid.so
mod_dir.so
mod_include.so
mod_log_config.so
mod_mime.so
mod_negotiation.so
mod_setenvif.so
mod_status.so
mod_suexec.so
mod_userdir.so
The suexec-related bugs i found in the apache bug database are
not related to what i'm reporting:
7810 suexec + userdir non-functional in httpd 2.0.35
7992 Core dump when restarting daemon with mod_suexec
8291 mod_include + mod_suexec has bug
7862 suexec never log a group name
7791 mod_suexec problem
8789 SuExec Log File does not get created by default when suexec
Running apache with 'LogLevel debug' did not reveal anything insightful.
I have no idea where to even begin looking through the apache source
code to try to resolve this problem, so i'm wondering if someone else
can please take a look. If you need any more information, please let
me know. Thank you very much for you time, and for the Apache server!!!
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org