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=15713>. 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=15713 suexec-logfile has hardcoded default instead of being placed in --logfiledir Summary: suexec-logfile has hardcoded default instead of being placed in --logfiledir Product: Apache httpd-2.0 Version: 2.0.43 Platform: PC OS/Version: Linux Status: NEW Severity: Minor Priority: Other Component: mod_suexec AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] If --with-suexec-logfile=FILE isn't specified in configure, the default is set by: suexec.h:#define AP_LOG_EXEC "/usr/local/apache2/logs/cgi.log" /* Need me? */ instead of suexec_log "in your standard logfile directory (--logfiledir)." as specified in the documentation (http://httpd.apache.org/docs-2.0/suexec.html). Therefor on my system where I chose a different prefix and logfile dir and /usr/local/apache2 does not exist, suexec does not function correctly (virtualhost cgi's give internal server errors) and (i think) userdir cgi's run as the apache user. Plus in the main server's error logs, we get: failed to open log file fopen: No such file or directory from suexec.c. Again, this is only the default and the obvious workaround is to specify --with-suexec-logfile=FILE in configure. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
