Some other comments. Firstly, I am not that familiar with apache, and so have never heard of apache2ctl. All I know is that on at least Debian/Ubuntu systems, the convention for starting a service is to use /etc/init.d. So when this doesn't work, it is more than a minor annoyance.
Secondly, the /etc/default/apache2 file says that NO_START controls boot behaviour, so why is it affecting behaviour when I try to start it myself? I agree that boot behaviour should be controlled by runlevels, but think Adam Conrad has a very good point about people like me not knowing how to restore the runlevel scripts. Therefore, I think the proposal by dAniel hAhler is the best. Third, if the contents of /etc/default are dependent on what is bound to port 80 at install time, then there should DEFINITELY be a comment in there which says as much. In my case I assume it was apache that was bound to port 80. I only removed apache after installing apache2. -- /etc/default/apache2: NO_START https://bugs.launchpad.net/bugs/21377 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
