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 84799 - killall script doesn't recognise parameters
killall script doesn't recognise parameters
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-02-21 09:49 EST by Dave Shield
Modified: 2014-03-16 22:34 EDT (History)
2 users (show)

See Also:
Fixed In Version: 7.31-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-09-03 21:42:34 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 Dave Shield 2003-02-21 09:49:08 EST
Description of problem:
Most of the scripts in /etc/rc.d/init.d take a command-line parameter
to control what operation to perform (start, stop, restart, status, etc)
The 'killall' script does not - it simply starts shutting down all
remaining services.

In normal situations, this will only ever be called as part of the
shutdown procedure (as "killall start").   But given the drastic
nature of the behaviour of this script, this should be checked for.
If nothing else, running 'killall status' should return an error
message, rather than starting to shut down the services.

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

How reproducible:
very (and very cautiously!)

Steps to Reproduce:
1. /etc/rc.d/init.d/killall status
Actual results:
Shutting down APM daemon:       [OK]

Expected results:
Usage: killall {start}
   (by analogy with the 'halt' script)

Additional info:
initscripts-6.67-1 (RH7.3) also shows the same behaviour.
Probably earlier versions as well.
Comment 1 Bill Nottingham 2003-09-03 21:42:34 EDT
Fixed, will be in 7.31-1; thanks!

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