Bug 84799

Summary: killall script doesn't recognise parameters
Product: [Retired] Red Hat Linux Reporter: Dave Shield <d.t.shield>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: mitr, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 7.31-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-09-04 01:42:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dave Shield 2003-02-21 14:49:08 UTC
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):
initscripts-6.59.1

How reproducible:
very (and very cautiously!)

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

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-04 01:42:34 UTC
Fixed, will be in 7.31-1; thanks!