Bug 97925 - kill_proc in /etc/init.d/functions doesn't work when there is space in the command name
Summary: kill_proc in /etc/init.d/functions doesn't work when there is space in the c...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 9
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-24 06:33 UTC by eli morris
Modified: 2014-03-17 02:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-30 19:06:56 UTC
Embargoed:


Attachments (Terms of Use)

Description eli morris 2003-06-24 06:33:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130

Description of problem:
The command killproc 'java -cp /home/ucsc/programs XferClient' (just as an
example.) worked under redhat 7.2 and 7.3, but now it doesn't because the
command contains whitespace in it.

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


How reproducible:
Always

Steps to Reproduce:
1. Write a program that runs forever. i.e. an endless loop. Name the command
something with whitespace in it. Java programs automatically fit this
description, because the usual execution is 'java program-name'
2.Create init script that starts the program running as a daemon, then stop this
program using 'killproc'
3. Run script
    

Actual Results:  killproc fails with an error message. 

Expected Results:  Program should successfully die.

Additional info:

Program would start and stop normally under redhat 7.2 and 7.3. The new killproc
function in redhat 9 (maybe 8 also?) doesn't like program names with whitespace
in them, even if qouted. Workaround is to use the functions script from redhat
7.2 for these type of commands.

Comment 1 Bill Nottingham 2005-09-30 19:06:56 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

Please attempt to reproduce on a current release, such as Fedora Core 4. If this
issue persists, please open a new bug.


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