Apache does not start due to a missing library. In the init script this is incorrectly called "a syntax error in your configuration files" if [ $ret -ne 0 ]; then eerror "${SVCNAME} has detected a syntax error in your configuration files:" ${APACHE2} ${APACHE2_OPTS} -t fi Reproducible: Always
Last time I checked, initscripts were not supposed to do revdep-rebuild's job.
Last time I checked, error messages were supposed to be correct. There are probably a trillion reasons for apache2 returning non-zero that have nothing to do with syntax errors in configuration files.
Would a message: "apache has failed to start for a mysterious reason" satisfy you ? If your system is in good state, syntax errors are the most likely reason of failure. If it fails to run due to missing libraries, it means you've failed to revdep-rebuild.
I apologize for trying to improve something. Please disregard my comments.
(In reply to comment #4) > I apologize for trying to improve something. Please disregard my comments. Please don't assume that the other poster is representing Gentoo. If you would like to submit a patch for the configuration file, this bug may be better received.
I may not be representing Gentoo, but still implementing whatever revdep-rebuild does to detect broken linking *in an init script* doesn't look like a good idea.
All I was saying is that a nonzero return value does not automatically imply a syntax error in the configuration file. I don't know a lot of init-scripts that do more than a simple check if the service could be started or not. It is up to the user to find out why something has failed. Claiming that it is a syntax error in the configuration file seems to be unfounded. I just stumbled upon it during a library issue, I'm not saying that an init script should detect something like that.
fixed in 2.2.15, thanks
