Bug 28628

Summary:	'init 1' no longer works
Product:	[Retired] Red Hat Linux	Reporter:	Ed McKenzie <eem12>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-02-21 16:52:55 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 Ed McKenzie 2001-02-21 16:52:52 UTC

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 16:54:51 UTC

This was hacked around in a later initscripts release. AFAICT, it's a kernel
problem.

Comment 2 Bill Nottingham 2001-02-21 16:55:14 UTC

(basically, remove the 'exec' from the last line of init.d/single)