Red Hat Bugzilla – Bug 60689
/etc/init.d/halt doesn't take standard init-script arguments
Last modified: 2014-03-16 22:25:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205
Description of problem:
The /etc/init.d/halt script doesn't follow the init.d standard of
start-stop-status. While "start" and "stop" admittedly aren't useful for
halt, it means an unpleasant surprise when you start with the
impression that calling an init script with the "status" argument
doesn't change system or service state.
Since halt is called as rc0.d/S10halt, halt should run on "halt
start", with "halt stop" and "halt status" being noops.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Simple: /etc/init.d/halt status
Real-world example that bit me, after noticing some services didn't
start after reboot when I expected them to:
for i in /etc/init.d/*; do $i status; done
Actual Results: System halted.
Expected Results: Something nondestructive; perhaps a status report, perhaps an
error message, perhaps a noop.
The same problem exists in /etc/init.d/killall and /etc/init.d/single.
Checked a 7.2-ish system, and this has been resolved at some point after
initscripts-5.49-1 and now. Nevermind. :-)