Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1866 - ntsysv does not show proper "levels"
Summary: ntsysv does not show proper "levels"
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-03-29 15:50 UTC by Stephen John Smoogen
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-03-29 16:00:08 UTC

Attachments (Terms of Use)

Description Stephen John Smoogen 1999-03-29 15:50:06 UTC
If you log in as single user (LILO linux single) and run
ntsysv to change application run levels it shows all
connections to be blank [ ] versus what they might be
running at all.

While this might be intended behaviour it does not fit older
behavior where ntsysv would show what applications would
generally run. This gave users an easy tool to turn off
applications that might cause problems if they tried to
start the machine in run level 3 or 5.


Comment 1 Bill Nottingham 1999-03-29 16:00:59 UTC
This is a behavior change, which is documented in the
man page. To edit a particular runlevel, do
'ntsysv --levels 123', for example. Basically, the
problem we're facing is how to avoid accidentally turning
on X in runlevel 3. :(

Comment 2 Adam Thompson 1999-04-04 22:51:59 UTC
Simplest way I've seen (can't remember which OS) takes into account
the fact that there is (generally) a fixed upper bound on the number
of runlevels.  The ntsysv screen could be redone to look something
like this:

      | Default Runlevel: [3] |
| apmd     [X] [X] [X] [X] [X] [ ] [ ] [ ] [ ] |
| ....                                         |
| xdm      [ ] [ ] [ ] [ ] [X] [ ] [ ] [ ] [ ] |
        <<OK>>  <<CANCEL>>

I don't know what range of runlevels SysVinit can handle, so this may
or may not be practical.  Worth noting that a "typical" RedHat system
only worries about runlevels 0, 3, 5 and 6. (I think. :-)

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