Ryan, Actually, just renaming any services that you do not wish to run to norun.S$$foo is the method that many of us use. You're right in that deleting the scripts entirely is not desirable. But keeping track of the order in which they are to run, and disabling those you don't want running is fairly important.
That's my $0.02, anyway. Regards, Ben Pitzer --------------------------------------------- "Those that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." --Ben Franklin-- > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Ryan Leathers > Sent: Wednesday, December 03, 2003 9:17 AM > To: [EMAIL PROTECTED] > 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 <[EMAIL PROTECTED]> > 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
