I've found sysv-rc-conf is about as useful as it gets on deb/buntu and frankly can't stand their paradyme (of renaming S-to-K blah...) That's why I just chmod.
On RH though, chkconfig just plain does it all 'automagically' There's so much about 'untu in the /etc dept. that I find lacking. Softlink hell, etc/network/interfaces compared to the RH way in sysconfig ... I also like the way RH applies init.d/scriptname status where deb/untu does not. Trivial really, to implement. Sometimes using the kludge is so much easier, specially when you install an app/service that you don't want started at boot, or ever FTM.. Rion On Saturday 24 January 2009, Anthony Carrico wrote: > Rubin Bennett wrote: > > The 'right' way is to rename the script from S99scriptname to > > s99scriptname. Scripts with a lowercase beginning character are > > automagically ignored by init. > > Brilliant. S's to start and K's stop. Lowercase s's are ignored, but > serve as a cache of disabled S's. Give that man a prize. > > > You can also 'chkconfig scriptname off' if your system uses chkconfig. > > You can tell if it uses chkconfig by running 'chkconfig scriptname > > --list' > > A foreigner on Debian (and its derivatives like Ubuntu), but > sysv-rc-conf is closest, and sysv-rc-conf caches values in > /var/lib/sysv-rc-conf/services. One side effect of that is --list > doesn't work until root runs it. I think changing s-to-S or S-to-s would > be nicer. I didn't see anything sanctioning the lowercase s in the > Debian manuals, so that may be the reason. >
signature.asc
Description: This is a digitally signed message part.
