Bug 4235 – globus-job-manager doesn't exit if the job fails.

Bug 4235 - globus-job-manager doesn't exit if the job fails.

Summary:

globus-job-manager doesn't exit if the job fails.

Status:	RESOLVED INVALID

Product:	GRAM
Component:	gt2 Gatekeeper/Jobmanager
Version:	4.0.1
Platform:	PC Linux

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Stuart Martin

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-02-24 05:03 by Tatsuhiko Inoue
Modified:	2011-12-14 08:06 (History)

Attachments
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 Tatsuhiko Inoue 2006-02-24 05:03:35

globus-job-manager process doesn't exit on remote host,after the job fails.

In case meeting the following two conditions, the job submission of PreWS GRAM
is failed as a matter of course.
- The name of client host has not been registered to DNS.
- stdout and stderr are transferred from remote host to client host.

Then, globus-job-manager process doesn't exit in remote host.

This probrem occurred, when the following command on the host whose
name has not been registered to DNS.
 % globusrun -o -r "remotehost.org" '&(executable=/bin/hostname)'

------- Comment #1 From Joe Bester 2011-12-14 08:06:55 -------

Sorry we were unable to visit this issue. lease reopen if this bothers you in a
more recent release.