Aaron Konstam wrote: > On Wed, 2007-07-04 at 16:10 -0500, Mikkel L. Ellertson wrote: > <snip> >> I do not see how running "chlconfg NetworkManagerDispatcher on" >> instead of "chkconfig --level 35 NetworkManagerDispatcher on" would >> confuse people. Having things set properly for the run levels that >> they do not normally use is a bonus - if they end up using them in >> troubleshooting, things are already set up for them without them >> having to think about it. >> > Ok, lets not argue about it. Just tell me when was the last time you ran > your machine in runlevel 2 or 4, and why was that needed? > Run level 4 - Monday. I have a test server that starts one set of services if I start in run level 3, and a different set if I run in run level 4. If I run it in run level 5, I can use it as a workstation. I do not use run level 2 very often. I use run level 1 more often for fixing problems. Run level 2 is not a clean non-networking level any more. Then again, you get users that never boot anything except run level 5. They also use the system-config-services GUI to control what services are run. Unless they use the run level editor, it is the same as running chkconfig <service> on when they enable a service. Chkconfig then uses the header information form the daemon control file in /etc/rc.d/init.d to determine both the run levels and start/stop order value for the daemon. I guess you and I look at things differently. I feel that the defaults are there for a reason. I am not going to blindly override them. But I will make make informed choices to override them. I feel that always running chkconfig --level 35 <service> is risking problems without adding value. If you know you want the service to run in run levels 3 and 5, and only run levels 3 and 5, that is a different story. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
