DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39973>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39973 ------- Additional Comments From [EMAIL PROTECTED] 2006-07-06 15:16 ------- >If the apachectl -d option does exist Here's the clue: If apachectl doesn't see its traditional init script-style parameter (start/stop/restart/etc.), it assumes the command-line consists of httpd parameters, and passes them straight through to httpd. That, and the fact that httpd is a non-portable* way to start Apache 2+, are not clear from the documentation. *httpd may work perfectly, may not start at all, or may appear to work but with suboptimal settings, depending on the platform and exactly how Apache was built If we rework apachectl to expand its use, we should keep in mind some of the confusion which has occurred with Apache 2+ with httpd options vs. apachectl options, including confusion of users of binary builds which require apachectl. The idea that apachectl is primarily an init script and should be symlinked to the proper rc directory, or run directly with the familiar init script command-line, is a nice simplification. Also, for every web server install a suitable apachectl will be created which already has the proper install path. Separately there is a value in a lower-level interface, but which unlike the current httpd executable, also picks up the required settings from envvars, so that the same low-level command-line works for source users and binbuild users and everything in-between. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
