Bug 69359

Summary: SysVinit-2.84-4: "telinit s" doesn't stop services
Product: [Retired] Red Hat Raw Hide Reporter: Jonathan Kamens <jik>
Component: SysVinitAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: 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: 2005-01-28 06:06:41 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 Jonathan Kamens 2002-07-22 12:38:57 UTC
This morning I ran "telinit s" (or perhaps "telinit S", I'm not sure which,
although I'm pretty sure it wasn't "telinit 1") to go to single-user mode.  Init
didn't run any of the stop scripts it should have run when switching from
runlevel 5 to runlevel 1.

Comment 1 Bill Nottingham 2002-07-22 15:19:10 UTC
The stop scripts are only run when you switch to runlevel 1; running 'telinit S'
doesn't actually switch runlevels.

Did this work before?

Comment 2 Jonathan Kamens 2002-07-22 15:24:59 UTC
"telinit s" is supposed to switch runlevels.  The man page claims that "telinit
S or "telinit s" should "tell init to switch to single user mode," which sure
sounds to me like it's supposed to switch runlevels, since I thought that the
definition of "single user mode" was "runlevel 1".

Yes, I'm pretty certain taht it worked before.

If it doesn't work properly, it should be disabled completely, i.e., "telinit s"
or "telinit S" should generate an error.


Comment 3 Bill Nottingham 2005-01-28 06:06:41 UTC
Closing out unresolved bugs on older, end-of-lifed releases.
Apologies for any lack of response.

At this point I don't think we're going to change the upstream/current
behavior.