From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)
Description of problem:
it would be /really/ nice being able to do:
# service xinetd disable
instead of using ntsysv, when I want to disable the
running of a service at boot time...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.# service xinetd disable
Actual Results: Usage: /etc/init.d/xinetd
Expected Results: The service xinetd has been disabled (it will not run
automatically at boot time)
Of course, you can always run:
chkconfig --level 345 <service> off
yes, I know...
but using the service command will be a /lot/ more intuitive,
(because I'm talking about a *service*, basically I'm saying:
"I want to disable this *service*")
note how I can stop, start, ask status, etc with the command
service, why should I use another command for disabling it ?
of course, this should not be a replace for chkconfig,
because this command may permit more granularity
I'm an RHCX, I can certainly say many customers find the name of the
'chkconfig' tool and the 'service' command's inability to handle
enabling / diabling services unintuitive.
Closing bugs on older, no longer supported, releases. Apologies for any lack of
Realistically, time spent on this is probably better spent on a better service
framework (such as one using dependencies, etc.).