Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 112667 - run level editor front end
run level editor front end
Product: Fedora
Classification: Fedora
Component: redhat-config-services (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-12-26 16:50 EST by Fred Hubbard
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-13 11:12:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fred Hubbard 2003-12-26 16:50:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
can we please have a built in front end for a run level editor

Version-Release number of selected component (if applicable):
all version

How reproducible:

Steps to Reproduce:
1.just boot up

Actual Results:  none

Expected Results:  none

Additional info:

nice to have
Comment 1 Daniel Walsh 2003-12-26 20:17:33 EST
Not really sure what you want,  Could you clarify it.

Comment 2 Fred Hubbard 2003-12-29 21:10:12 EST
dan, to edit the run levels of the system you have to manually do so
(levels 1-6). this is handy for telling the system at boot time what
devices, periferals, services etc you want started or not & at what
level at run time.

if you could do a grafical front end for this it would be nice if it
was located under control center, system administration.

hope this helps, Fred H.
Comment 3 Daniel Walsh 2003-12-30 07:54:18 EST
Ok, but by that definition.  system-config-services
(redhat-config-services) is the tool.  It allows you to configure
runlevels and the services that run (At least for run level 3,4,5).


Note You need to log in before you can comment on or make changes to this bug.