Re: "debian rookie" trying to get his bearings...
"Kent" == Kent West <email@example.com> writes:
Kent> Ron Johnson wrote:
>> The Unix Way [to disable automatic starting of init scripts] is
>> to rename S20apache to K20apache. That way, you can see what's
>> been explicitly turned off, and you'll know that if it's not in
>> /etc/rc2.d/ then it hasn't been installed.
>> Remeber to also rename /etc/rc6.d/K??apache !!!
Kent> How about renaming S20apache to NOS20apache? This way, you
Kent> can see at a glance which scripts are start scripts, which
Kent> are kill scripts, and which are scripts that have been
Kent> disabled by the sysadmin
This is not technically correct, because if you switch between
runlevels you will find that apache will not start and stop
correctly. Unless of course you want to do this at every multiuser
level (in which case Apache never starts).
The whole idea of having different run levels was to provide different
levels of service. So, for example, you could use a run level on a web
server to run apache, and have a multi-user 'maintenance' run level
where apache is stopped but everything else works. The most common
example of this is to have a run level with X running and one without