Bug 173572 - Manual page of inittab shows rc 0-6 runlevel inside /etc/init.d
Summary: Manual page of inittab shows rc 0-6 runlevel inside /etc/init.d
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: filesystem
Version: 4.0
Hardware: s390
OS: Linux
Target Milestone: ---
: ---
Assignee: Bill Nottingham
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-11-18 06:56 UTC by anupama
Modified: 2014-03-17 02:56 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2005-11-18 17:40:17 UTC

Attachments (Terms of Use)

Description anupama 2005-11-18 06:56:23 UTC
Description of problem:
The Manual page of  /etc/inittab shows the following

  # man inittab
/etc/init.d executes the S and K scripts upon change
         # of runlevel.
              # Runlevel 0 is halt.
              # Runlevel 1 is single-user.
              # Runlevels 2-5 are multi-user.
              # Runlevel 6 is reboot.

              l0:0:wait:/etc/init.d/rc 0
              l1:1:wait:/etc/init.d/rc 1
              l2:2:wait:/etc/init.d/rc 2
              l3:3:wait:/etc/init.d/rc 3
              l4:4:wait:/etc/init.d/rc 4
              l5:5:wait:/etc/init.d/rc 5
              l6:6:wait:/etc/init.d/rc 6

Actually , the runlevels in redhat are in 
   /etc/rc 0
  /etc/rc 1

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Bill Nottingham 2005-11-18 17:40:17 UTC
As the man page states, these are examples of what you can write, not what is
actually used, so it's not deemed a critical issue to fix this.

This problem will be resolved in the next release of Red Hat Enterprise Linux.
Red Hat does not currently plan to provide a resolution for this in a Red Hat
Enterprise Linux update for currently deployed systems.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects. 

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