preventing apache/-perl/-ssl from starting on upgrade .. possible "issue"
I followed the directions in the security guide on how to prevent the
symlinks from being re-added by the upgrade process. I did the
following prior to the recent security upgrade:
update-rc.d -f apache remove
update-rc.d apache stop 20 0 1 2 3 4 5 6 .
(for each apache, apache-perl and apache-ssl)
It succeeded in preventing the upgrade process from re-adding the
symlinks. The only other function I hoped it would provide is making it
so the upgrade process didn't attempt to start the apache* servers
again. Like I'd hoped it didn't attempt to start start apache or
apache-ssl (atleast as far as I can tell (no /var/log/apache[-ss] log
entries)). Hopefully because there was a stop link for my current
runlevel 2) but it did start apache-perl (I verified that stop links
were in place fore apache-perl). That kinda shot my theory to crap :(
I wanted to post this here (knowing full well its not a support list)
for two reasons:
1. I thought it might be a "bug" (forgive the terminology) since it
seemed to 'do the right thing' for apache and apache-ssl and since it
didn't for apache-perl.
2. Someone might know the correct way to achieve this result if I'm not
doing it correctly.
I posted on the debian-user list but I didn't get any useful responses.
-Matt
Reply to: