Bug 3582 – globus-stop-container-detached exits with non-0 on successful exit

Bug 3582 - globus-stop-container-detached exits with non-0 on successful exit

Summary:

globus-stop-container-detached exits with non-0 on successful exit

Status:	RESOLVED FIXED

Product:	Java WS Core
Component:	globus_wsrf_core
Version:	unspecified
Platform:	All All

Importance:	P3 minor
Target Milestone:	---
Assigned To:	Mats Rynge

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-07-21 09:36 by Mats Rynge
Modified:	2005-07-28 14:14 (History)

Attachments
Fix for stop-detached (1.65 KB, patch) 2005-07-21 09:43, Mats Rynge	Details
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Mats Rynge 2005-07-21 09:36:03

From the discuss list:

-------------------------------------------------------------------
I've noticed that executables for starting and stopping globus container
in GT4:
globus-start-container-detached
globus-stop-container-detached

are returning 1 weather the call was successful or not.

Example:
[globus@grozd.srce globus]$ globus-stop-container-detached;echo $?
Stopping Globus container. PID: 5959
Container stopped
1
[globus@grozd.srce globus]$ globus-stop-container-detached;echo $?
Stopping Globus container. PID: 5959
Stopping container failed
1

Is there a version on cvs which returns correct exit status?
-------------------------------------------------------------------


globus-start-container-detached has already been fixed, but
globus-stop-container-detached still has the problem.

------- Comment #1 From Mats Rynge 2005-07-21 09:43:57 -------

Created an attachment (id=659) [details]
Fix for stop-detached

Have to hold the fix because of 4.0.1 code freeze.

------- Comment #2 From Jarek Gawor 2005-07-28 14:14:55 -------

I committed the patch to trunk and globus_4_0_branch as it seems like a simple 
and useful change. 
The error code handling code is a little confusing to me and probably should be 
looked at, at some point (e.g. what's the reason for setting rc variable if it 
is not accessed anywhere?).