a quick scan through my /etc/rc.d/init.d/ directory revelaed the following: fgrep "chkconfig: -" * acpid:# chkconfig: - 55 10 amd:# chkconfig: - 72 28 arpwatch:# chkconfig: - 55 45 bootparamd:# chkconfig: - 60 20 ipchains:# chkconfig: - 08 92 ldap:# chkconfig: - 70 40 mars-nwe:# chkconfig: - 60 60 mcserv:# chkconfig: - 86 30 nfs:# chkconfig: - 60 20 nscd:# chkconfig: - 30 80 pulse:# chkconfig: - 60 10 rstatd:# chkconfig: - 60 20 rusersd:# chkconfig: - 60 20 smb:# chkconfig: - 91 35 snmpd:# chkconfig: - 50 50 squid:# chkconfig: - 90 25 xntpd:# chkconfig: - 55 10 All these services (some of them could already have been updated, my cooker is a bit lagging --> you guys work too hard!!) won't be set "on" when you do a chkconfig add <service>. There are no runlevels supplied that they should run in. Some of these services are insecure, but we shouldn't protect users against using them if that means that they can't turn it on when they want to. There's a difference between turned off by default in the distro (msec takes care of this?) and "it's impossible to turn it on". The user should be able to enable the service, if he (she?) _chooses_ to do so.... Just my 0.02 Euro... Stefan
