Bug 28628 - 'init 1' no longer works
'init 1' no longer works
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-21 11:52 EST by Ed McKenzie
Modified: 2014-03-16 22:19 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-21 11:52:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ed McKenzie 2001-02-21 11:52:52 EST
On fisher, both the beta release 5.59 and the rawhide 5.61 seem to be
broken with respect to runlevel 1 behavior. Issuing an 'init 1' from
runlevel 5 shuts down all services and prints a message to the effect of
'telling INIT to go to single-user mode' before hanging. After a few
seconds' pause, disk activity begins (no output to console) and gdm starts
up again. Very strange.

'init S' still seems to work.
Comment 1 Bill Nottingham 2001-02-21 11:54:51 EST
This was hacked around in a later initscripts release. AFAICT, it's a kernel
problem.
Comment 2 Bill Nottingham 2001-02-21 11:55:14 EST
(basically, remove the 'exec' from the last line of init.d/single)

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