Yes, CentOS 3.4 is based on RHEL 3 U4, and I tried that method... I also tried it in FC3 and someone else said they tried it in FC1 and it doesn't work.
I would seem to me that chkconfig xinetd off would turn off the xinetd SERVICE where as things like imap, pop3, and sgi_fam are parts of that service, thusly, must be handled individually as previously mentioned, disable=yes added to /etc/xinetd.d/sgi_fam If anyone experiences otherwise, please let me know. I'll be installing another CentOS 3.4 box today. Thanks, David McD On Fri, 28 Jan 2005 07:41:34 -0500, Steve Hoffman <[EMAIL PROTECTED]> wrote: > Isn't CentOS based on RHEL? It should have chkconfig then. > > Do a "chkconfig --list" to see how it's listed, probably sgi-fam! > the last set of lines is the services run in xinetd (no > runlevels..only on or off) sgi-fam is probably turned on > so do a "chkconfig sgi-fam off" and then restart xinetd...that's how I > turn those services on and off. > > Steve > > On Thu, 27 Jan 2005 15:28:31 -0500, Jeff Groves <[EMAIL PROTECTED]> wrote: > > Ooops! Misread. > > > > To disable, you want "disabled=yes" > > > > Sorry for the confusion, > > > > Jeff G. > > > > David McDowell wrote: > > > > >sgi-fam is a security-related daemon that can monitor system file > > >integrity and network access attempts. > > > > > >This is the basics of what I can find about this xinetd service. I'm > > >running CentOS 3.4 and also find sgi_fam to be annoying in FC3 as > > >well. In the end, what occurs is that I cannot umount a SMB share b/c > > >sgi_fam won't let it go. I forgot to take a note, but last time this > > >happened I did something like fuser kill with a couple options... > > >iirc. > > > > > >Anyway, the main point of my query is this: is sgi_fam necessary for > > >anything?? If not, I'd like to disable it completely as it keeps > > >getting in my way. In my attemps to do so, I seem to be failing to > > >disable it. I edited /etc/xinetd.d/sgi_fam and the top line is: > > > > > >#default: on > > > > > >so I figured I should add this line under that: > > > > > >default: off #since this line isn't commented it should work right? > > > > > >I did service xinetd restart and reload and neither caused sgi_fam to > > >turn off. I also happened to have a new kernel to boot to, so I > > >rebooted and sgi_fam is still on! > > > > > >thanks, > > >David McD > > > > > > > > > > -- > > Law of Procrastination: > > Procrastination avoids boredom; one never has > > the feeling that there is nothing important to do. > > > > -- > > 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 > > > -- > 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 > -- 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
