[gram-user] Bug in globus-job-run

[Jim Basney]

Hi Anand,

Are you submitting the job from osg-test-ce.ncsa.uiuc.edu? My guess is
you're submitting from a different machine where /ncsa/apps-local/itb
exists but /ncsa/apps-local/osg-itb-0.9.2 doesn't.

The local shell is going to expand the wildcard before passing it to
globus-job-run, unless you put the wildcard inside quotes.

-Jim

Anand Padmanabhan wrote:
> Hi,
> 
> I ran into a strange problem when when running a simple ls job through
> globus-job-run. It appears to have something to do with symlinks and
> wildcards.
> 
> Here is what I found
> $globus-job-run osg-test-ce.ncsa.uiuc.edu/jobmanager-fork /bin/ls
> /ncsa/apps-local/osg-itb-0.9.2/globus/TRUSTED_CA/*.0
> 
> fails (returns no such file or directory)
> 
> while
> 
> $globus-job-run osg-test-ce.ncsa.uiuc.edu/jobmanager-fork /bin/ls
> /ncsa/apps-local/itb/globus/TRUSTED_CA/*.0
> 
> returns results as expected.
> 
> The only difference between the two is a relative symlink (ln -s itb
> osg-itb-0.9.2). The strange thing is the TRUSTED_CA is also a symlink
> and that gets resolved.
> 
> Also
> $globus-job-run osg-test-ce.ncsa.uiuc.edu/jobmanager-fork /bin/ls
> /ncsa/apps-local/itb/globus/TRUSTED_CA
> 
> i.e. with symlink but without the wildcard returns correct results.
> 
> So essentially the problem appears to be caused when a relative symlink
> is used along with a wild card. I am not sure if this is a known issue,
> but a quick search on bugzilla did not reveal any thing. I was using
> following version
> $ globus-job-run -version
> globus-job-run: 4.7
> 
> Let me know if this is a known issue or should I submit a bug report.
> 
> Thanks,
> Anand
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3234 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.globus.org/pipermail/gram-user/attachments/20090617/f69aa9b5/attachment.bin>