If I do "/etc/init.d/apache2 start" and then "/etc/init.d/apache2 stop" very fast, close the terminal, and then tries to start Apache again nothing will happen. "/etc/init.d/apache2 start" will just give a new empty line and won't start Apache at all. The solution is to kill the runscript process that has gone stuck. However, I thought "/etc/init.d/apache2 zap" should do that, but it didn't. Perhaps it would be a good idea to make zap look after stuck runscript-processes and kill them?
*** This bug has been marked as a duplicate of bug 160677 ***