Here's what "find /etc/rc* -name '*apache*'" produces:
/etc/rc0.d/K09apache2
/etc/rc1.d/K09apache2
/etc/rc2.d/S91apache2
/etc/rc3.d/S91apache2
/etc/rc4.d/S91apache2
/etc/rc5.d/S91apache2
/etc/rc6.d/K09apache2
An Internet search reveals this link:
http://serverfault.com/questions/250270/apache-starts-automatically-on-ubuntu-needs-to-be-stopped-to-restart-lighttpd
Which suggests cleaning things up a bit:
Accordingly, I ran "sudo update-rc.d apache2 disable" with these perplexing
results:
update-rc.d: warning: start runlevel arguments (none) do not match apache2
Default-Start values (2 3 4 5)
update-rc.d: warning: stop runlevel arguments (none) do not match apache2
Default-Stop values (0 1 6)
Disabling system startup links for /etc/init.d/apache2 ...
Removing any system startup links for /etc/init.d/apache2 ...
/etc/rc0.d/K09apache2
/etc/rc1.d/K09apache2
/etc/rc2.d/S91apache2
/etc/rc3.d/S91apache2
/etc/rc4.d/S91apache2
/etc/rc5.d/S91apache2
/etc/rc6.d/K09apache2
Adding system startup for /etc/init.d/apache2 ...
/etc/rc0.d/K09apache2 -> ../init.d/apache2
/etc/rc1.d/K09apache2 -> ../init.d/apache2
/etc/rc6.d/K09apache2 -> ../init.d/apache2
/etc/rc2.d/K09apache2 -> ../init.d/apache2
/etc/rc3.d/K09apache2 -> ../init.d/apache2
/etc/rc4.d/K09apache2 -> ../init.d/apache2
/etc/rc5.d/K09apache2 -> ../init.d/apache2
Now I ran "find /etc/rc* -name '*apache*'" again:
/etc/rc0.d/K09apache2
/etc/rc1.d/K09apache2
/etc/rc2.d/K09apache2
/etc/rc3.d/K09apache2
/etc/rc4.d/K09apache2
/etc/rc5.d/K09apache2
/etc/rc6.d/K09apache2
And trying the "sudo update-rc.d apache2 disable" trick yet again:
update-rc.d: warning: start runlevel arguments (none) do not match apache2
Default-Start values (2 3 4 5)
update-rc.d: warning: stop runlevel arguments (none) do not match apache2
Default-Stop values (0 1 6)
Disabling system startup links for /etc/init.d/apache2 ...
Removing any system startup links for /etc/init.d/apache2 ...
/etc/rc0.d/K09apache2
/etc/rc1.d/K09apache2
/etc/rc2.d/K09apache2
/etc/rc3.d/K09apache2
/etc/rc4.d/K09apache2
/etc/rc5.d/K09apache2
/etc/rc6.d/K09apache2
Adding system startup for /etc/init.d/apache2 ...
/etc/rc0.d/K09apache2 -> ../init.d/apache2
/etc/rc1.d/K09apache2 -> ../init.d/apache2
/etc/rc6.d/K09apache2 -> ../init.d/apache2
/etc/rc2.d/K09apache2 -> ../init.d/apache2
/etc/rc3.d/K09apache2 -> ../init.d/apache2
/etc/rc4.d/K09apache2 -> ../init.d/apache2
/etc/rc5.d/K09apache2 -> ../init.d/apache2
Which brings us full circle with Trisquel still trying to run the unwelcome
apache2.
Originally I removed apache2 with "sudo apt-get remove apache2" and "sudo
apt-get remove apache2-data" and re-running these two commands shows that
they're still "away" as in "thrown away."
Should I run "sudo apt-get purge apache2 apache2-data" ? I have no need for a
server and do not want the dubious activity of any surreptitious activation
of apache. Which is why I'm still perplexed about those blinky messages that
appear now & then on this laptop as well as on three other Trisquel 7
installations of mine. Are they telling me that Trisquel is calling the
mother ship like Windows 3.11 used to do ? I still remember hearing my modem
up and calling who-knows-whom while Windows 3.11 was sitting there on my desk
with no intervention that I knew about twenty-some years ago ...
