Bug 346261 - halt initscript not responding to halt/poweroff instructions from shutdown
Summary: halt initscript not responding to halt/poweroff instructions from shutdown
Keywords:
Status: CLOSED DUPLICATE of bug 475227
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-23 04:56 UTC by Daphne Shaw
Modified: 2014-03-17 03:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-16 17:10:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
A patch for /etc/rc.d/init.d/halt (406 bytes, patch)
2007-10-23 04:57 UTC, Daphne Shaw
no flags Details | Diff

Description Daphne Shaw 2007-10-23 04:56:40 UTC
Description of problem:

The shutdown command provides the -H and -P flags that can be used alongside -h
to tell the system to halt or poweroff, respectively.  The halt initscript in F7
is not looking at this, and so (outside of a possible /halt file) always powers off.

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

initscripts-8.54.1-1

Steps to Reproduce:
1. Do "shutdown -h -H now"
2. Note that the machine powers off (rather than halting).

Comment 1 Daphne Shaw 2007-10-23 04:57:45 UTC
Created attachment 234721 [details]
A patch for /etc/rc.d/init.d/halt

Here's one way to fix it.

Comment 2 Bug Zapper 2008-05-14 14:49:51 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Daphne Shaw 2008-05-14 18:33:17 UTC
Confirming this still exists in F9 with initscripts-8.76.1-1.x86_64.

Comment 4 iarly selbir 2009-03-15 01:39:23 UTC
is this problem happening yet?

Give us a feedback.

Thanks.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 Daphne Shaw 2009-03-15 01:55:17 UTC
(In reply to comment #4)
> is this problem happening yet?
> 
> Give us a feedback.

I'm afraid I don't understand what you are asking me.  Are you asking if the problem still exists in F10?  If so, yes, it does.  The halt from initscripts-8.86-1.i386 still does a poweroff instead of a halt.

Comment 6 iarly selbir 2009-03-15 02:02:15 UTC
I just want keep your report alive.

Thanks for your reply.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Bill Nottingham 2009-03-16 17:10:19 UTC

*** This bug has been marked as a duplicate of bug 475227 ***


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