Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 17907 - shutdown does not powerdown
shutdown does not powerdown
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2000-09-29 17:07 EDT by Need Real Name
Modified: 2014-03-16 22:16 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-09-29 23:47:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-09-29 17:07:19 EDT
After upgrading from 6.2 to 7, running "shutdown -h now" no longer shuts
down the machine and powers down the machine.  It just shuts down and I
have to manually power down.

I checked /etc/rc.d/init.d/halt and found that at the end of the file halt
is only given the -p option (necessary to powerdown the machine) if the
following is true:
[ -f /poweroff -o ! -f /halt ]

I added an "ls /" command before that line to see what files were in my
root directory at the time of shutdown and I found that /powerdown didn't
exist but /halt did exist.  I assume "/halt" was created temporarily by

Is this a change in behavior?  Do I have to create /powerdown if I want
shutdown to also powerdown the machine?

In any case, commenting out the final conditional, so that -p was always
added as an option, solved my problem.
Comment 1 Alan Cox 2000-10-01 18:38:30 EDT
I believe running 'poweroff' will do what you want.
Comment 2 Need Real Name 2000-10-02 15:41:17 EDT

So I guess:
"shutdown -h now" ==> "/sbin/powerdown"
"shutdown -r now" ==> "/sbin/reboot"
halt but no powerdown ==> "/sbin/halt"

Does this change have to be documented anywhere?

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