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=42207>. 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=42207 ------- Additional Comments From [EMAIL PROTECTED] 2007-04-24 08:21 ------- Perhaps a Suse 10.2 specific problem. Suse 10.2 uses rcapache2 instead of apachectl (it is named apache2ctl under Suse 10.2). From the Suse documentation Even if it is a Suse specific problem that Suse has caused and needs to know about, I still think better error output is needed. Such as "Could not start an ssl httpd2 on port 443 because of XX". I'm nearly certain the syntax is correct because it works when calling the init.d process directly with -D SSL. --- Tried to review doc on apache.org for the start script and not sure how to start. On apache.org, you will find 'apachectl' referenced as the standard tool to start apache2. Although this tool is available on SuSE Linux (named "apache2ctl"), using our slightly more powerful (and better integrated) tool named "rcapache2" is recommended. (That's actually the shell script /etc/init.d/apache2.) Enter "rcapache2 help" as user root to see what it can do. To start apache2, either enter "rcapache2 start" as root or use the YaST Runlevel Editor to activate the starting of apache2 at boot time. As a command line alternative to the Runlevel Editor, you could run the command "chkconfig -a apache2" to make sure that apache2 is started at system boot time. --- -- 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]
