GRAM only provides input files at the start of the job. How does that
application get the intermediate input? From a file? If so, then
perhaps you can transfer a file via GridFTP to a location where the
application could read it.
-Stu
On Feb 10, 2009, at Feb 10, 4:42 AM, induru hemanth wrote:
Hi
thank u sir ,now its working fine
But i have a small problem ,
I developed a shell program ,it takes more inputs
some inputs at starting and some more inputs at intermediate stage
how i can manage this job
please help me
thanking you
Hemanth
BIT
Mesra
On 2/7/09, Martin Feller <[email protected]> wrote:
Does vikas.sh specify the shell that shall be used for
interpretation of the script in the first line?
(something like #!/bin/sh)
Google says:
From the man page for exec(2):
"On the first line of an interpreter script, following the "#!", is
the name
of a program which should be used to interpret the contents of the
file. For
instance, if the first line contains "#! /bin/sh", then the
contents of the
file are executed as a shell script."
You can get away without this, but you shouldn't. All good scripts
state the
interpretor explicitly. Long ago there was just one (the Bourne
Shell) but
these
days there are many interpretors -- Csh, Ksh, Bash, and others.
Martin
induru hemanth wrote:
hi friends,
while i am submitting interactive job "vikas.sh"
[ba...@g3 ~]$ globusrun-ws -submit -c vikas.sh
Submitting job...Done.
Job ID: uuid:ee1b6690-f4d0-11dd-8403-001ec94af11c
Termination time: 02/07/3009 04:36 GMT
Current job state: Failed
Destroying job...Done.
globusrun-ws: Job failed: The executable could not be started.
starter: the job failed when the job manager attempted to run it
[ba...@g3 ~]$
But GRAM was working fine with jobs like "/bin/touch"
please help me,
Hemanth
Reddy
BIT
mesra
