First Last Prev Next    No search results available
Bug 4768 - Default scratch directory not created by WS-GRAM
: Default scratch directory not created by WS-GRAM
Status: RESOLVED DUPLICATE of bug 3803
: GRAM
general
: 4.0.1
: PC Linux
: P3 normal
: 4.0.4
Assigned To:
:
:
:
:
  Show dependency tree / graph
 
Reported: 2006-10-12 10:58 by
Modified: 2006-10-12 11:13 (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 2006-10-12 10:58:36 
[greenc@fgtest1] ~ $ globus-job-run-ws fgtest1.fnal.gov:9443 /usr/bin/whoami
globusrun-ws: Job failed: Invalid directory path
"/home/minboone/.globus/scratch/951bbe9e-3714-41a0-68b6-a02bbee41159/".
org.globus.exec.generated.InvalidPathFaultType

If the /home/minboone/.globus/scratch directory is created manually:

[root@fgtest1 ~]# ls -ld /home/minboone/.globus/scratch
drwx------  2 minboone e898 2048 Oct  9 12:36 /home/minboone/.globus/scratch

Then the command succeeds:

[greenc@fgtest1] ~ $ globus-job-run-ws fgtest1.fnal.gov:9443 /usr/bin/whoami
minboone

I would submit that the default behavior should be to ensure that the scratch
directory exists prior to creating the unique directory underneath it, as is
currently the case for pre-WS operation as I understand it. Otherwise, admin
intervention may be needed on a per-user basis.

Thanks for your time and help,
Chris.
------- Comment #1 From 2006-10-12 11:13:26 ------- 
This behavior was intentional since we aren't using the GASS cache anymore and
a common base scratch directory may be specified by the admin that shouldn't be
manipulated on a per-user basis. That said, other users have complained about
this behavior so we're trying to decide what the best way to handle this is.
I'm marking this as a duplicate of bug #3803.

*** This bug has been marked as a duplicate of 3803 ***
First Last Prev Next    No search results available