} } chkconfig --list | awk '{print $1}' | man } } I know that doesn't work, but my point is: Take the list you made, } identify the items you don't know, "man" them. } } For those that don't make sense, use a search engine to find the home } page and read about it. } } Still lost on some, ask about that remaining list of packages. Asking } directly may be easier, but it won't help at 3:00 AM when the server } crashes because rpcsvcgssd is hogging all CPU because it freaked out } and you don't know if you can shut it off safely... } } Regards, } Greg

thank you.

i fully understand what you are saying and i should have anticipated this better... what i should have asked was this...

out of that list, is there anything i shouldnt turn off under any circumstances for a typical DNS server on the Internet running the few other TCP/IP services it is offering?

notice i mentioned that i can pry dust portmap and any other rpc-* stuffs?

i have already done what you asked before and over the last 10 years many times.... and even more in the last year. yet...

things change a bit over time and so i was seeking advise other than go figure it out yourself. i am smart enough to deal with 3am server crashes...

see below as the thing is... i like to do my work well before and labor at never having a 3am server crash. :->

remember?? before last year i ran Slackware 1.2.13 and some Redhat 2.0.X stuff very "solidly" for 6 - 9 years and am just now migrating to newer hardware and opsys distribution versions...

thanks in advance and kind regards

- rh

-- Robert Hanson Abba Communications http://www.abbacomm.net

} } I typically switch off the following... } } chkconfig portmap off } chkconfig nfslock off } chkconfig rpcsvcgssd off } chkconfig rpcgssd off } chkconfig rpcidmapd off } chkconfig isdn off } chkconfig gpm off } chkconfig pcmcia off } chkconfig apmd off } chkconfig lm_sensors off } } If you want more info as to the purposes of each package, in addition } to reading the man pages as suggested by others, the package } information database contains a nice precis too... } } /sbin/chkconfig --list | grep ':on' | awk '{ print $1 }' | xargs rpm -qi } } Will.

thank you, some truly useful info and i appreciate the suggestions from others to do more man pages and searching as well.

it is a good idea to pipe Will's helpful commands above to "more" or a file though...

arent some things almost a waste of bits at times? ;->

shouldnt a lot of this be toggled off by default in an install? :)

Will, when using what you have above, it wont find things that actually correlate to "named" and "cpuspeed" etc...

is this "buggies" in the install or naming conventions or just funky renaming or?

thanks

- rh

-- Robert Hanson Abba Communications http://www.abbacomm.net

On 30/08/05, Robert Hanson roberth@abbacomm.net wrote:

Will, when using what you have above, it wont find things that actually correlate to "named" and "cpuspeed" etc...

Well, the stuff listed in the output of chkconfig relates to startup files in /etc/rc.d/init.d/ and symlinks to them from the appropriate run levels.

If the package name doesn't directly correlate with corresponding init script in init.d/ name-wise you can find out which package the startup scripts belongs to with

rpm -qfi /etc/rc.d/init.d/$script_name

As Johnny says, the defaults are RHEL's.

Will.