Bug 3899 - globus-stop-container-detached doesn't give the container the chance to finish normally
: globus-stop-container-detached doesn't give the container the chance to finis...
Status: RESOLVED FIXED
: Java WS Core
globus_wsrf_core
: unspecified
: PC Windows XP
: P3 major
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-11-09 10:26 by
Modified: 2005-11-17 14:11 (History)


Attachments


Note

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


Description From 2005-11-09 10:26:54
The globus-stop-container-detached first sends SIGTERM signal and then almost 
immediately sends the SIGKILL signal. That does not give the container enough 
time to finish it's normal shutdown procedure. The globus-stop-container-
detached should wait for the process to exit for a bit before issuing the 
SIGKILL signal.
------- Comment #1 From 2005-11-17 14:11:09 -------
Fix commited to globus_4_0_branch and HEAD.

It will first send SIGTERM. If the container has not exited by itself after 2
minutes, SIGKILL will be sent.