-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gordon Messmer wrote: > No, it doesn't. "chkconfig --add" won't do anything unless the service > hasn't been added yet. "chkconfig" by itself won't do anything, period. > > If you want to enable a service, you use "chkconfig <service> on", and > if you want to look at its configuration you use "chkconfig --list > <service>".
Clearly you're right. This must be a difference between the "real" chkconfig on redhat and the "fake" one that suse (which I'm running) has for all us ex-redhat users. :-) batman:~ # chkconfig xinetd xinetd off batman:~ # chkconfig --add xinetd xinetd 0:off 1:off 2:off 3:on 4:off 5:on 6:off Thanks for the explanation. I've kind of wondered about this. It explains why some of the chkconfig commands in the courier.spec file work fine but others I had to change to use the suse 'insserv' command. Jeff Jansen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDsup4ZxtYeNk78A8RAvKIAJ9JGLK4CH/2PpcOu0/lmLUgsuy/ywCg1EVX mycvOTyWYbfy1lWEUWeGLf0= =Nhgz -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
