Bug 56669
Summary: | service foobar disable | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <sergio_kessler> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | rvokal |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-29 19:21:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-11-23 20:05:47 UTC
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 (user-levels)... 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 response. Realistically, time spent on this is probably better spent on a better service framework (such as one using dependencies, etc.). |