How to stop unwanted servrices during boot

[Neil Woolford]

At 19:12 16/11/04, you wrote:

>I have to weigh in and side with the faction that considers removing the 
>executable bit on an init script a HORRIBLE hack.

I agree;  as a newcomer to Linux I think I have more trouble with aspects 
of the file modes/permissions than anything else.  Deliberately resetting 
one to stop something working could be very hard to sort out later.

>It's not that hard to just delete symlinks from /etc/rc5.d.  Users who 
>want something to not run can either delete them from that directory, or 
>in the event it might be desirable to have them start at boot again, just 
>move them elsewhere for safekeeping.
>
>...ROMeyn

My copy of Brian Ward's "How Linux Works" suggests mangling the names of 
the symbolic links in the appropriate rc*.d directories.

Specifically he suggests prefixing them with an underscore.

Hence, for example [..]/rc2.d/S50servicename would become 
[..]/rc2.d/_S50servicename.  Still easy to read for humans, and easy for 
them to reinstate, but won't get run by machine
processes that are looking for files starting S for start or K for kill.

I appreciate that this won't solve the problem with installation updates 
that amend or replace scripts in the rc*.d directories;  however, if the 
likely result of an install/update process is the installation of a fresh 
copy of a name-mangled script, this will be an obvious alteration as the 
directory listing will show both the normal (new) and mangled (previous) 
versions of the filename.

Neil  
-------------- next part --------------

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.782 / Virus Database: 528 - Release Date: 22/10/04