[TriLUG] rc.X -- how do the real sysadmins do it?

John Turner jdturner at nc.rr.com
Wed Dec 3 10:17:13 EST 2003


On some systems  it is common to have all the scripts in /etc/init.d 
and just have links in /etc/rc?.d. So to remove something just remove 
the link in /etc/rc?.d, but not the original in /etc/init.d. This give 
you the ability to start/stop manually but not when changing run 
levels.

John

>
>> -----Original Message-----
>> From: trilug-bounces at trilug.org [mailto:trilug-bounces at trilug.org]On
>> Behalf Of Ryan Leathers
>> Sent: Wednesday, December 03, 2003 9:17 AM
>> To: trilug at trilug.org
>> Subject: [TriLUG] rc.X -- how do the real sysadmins do it?
>>
>>
>> I'm installing a spanking new "big iron" cluster using Redhat ES 2.1
>> This morning I'm looking at security and part of this includes 
>> removing
>> some non-essential services from rc3 and rc5 on each host.  After the
>> stock install there were a slew of things being run.
>>
>> Now I'm wondering... rather than just removing the scripts I don't 
>> want
>> is there some convention I should be following to retain these scripts
>> that are not actively used?  I could come up with my own system, but
>> since this cluster will likely be around long after I'm gone I want to
>> do my successors a favor and observe convention if it exists.
>>
>> Wisdom appreciated.
>>
>> --
>> Ryan Leathers <ryan.leathers at globalknowledge.com>
>> Global Knowledge
>>
>
> -- 
> TriLUG mailing list        : 
> http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>




More information about the TriLUG mailing list