Hi all,
one user reports that he cannot submit a job with a JDL like:
$ cat test.jdl
[
Executable = "$VO_VO_PAUS_PIC_ES_SW_DIR/bin/python";
Arguments = "-V";
[...]
The wrapper is modifying it's Executbale adding an extra "./" to the
beggining of his Executable line. From it's CE wrapper file:
__executable=./$VO_VO_PAUS_PIC_ES_SW_DIR/bin/python
__cmd_line="\"./\$VO_VO_PAUS_PIC_ES_SW_DIR/bin/python\" -V\$* > \"std.out\" 2> \"std.err\""
If the command is sent as:
Executable = "/software/vo.paus.pic.es/bin/python"
that extar "./" is not added:
__executable=/software/vo.paus.pic.es/bin/python
__cmd_line="\"/software/vo.paus.pic.es/bin/python\" -V\$* > \"std.out\" 2> \"std.err\""
I guess that the extra "./" is some kind of relative/absolute
path protection for user (something like: if the command does
not starts with "/" is a user mistake and we must refer it as relative
path).
Is that true? is there any way for bypassing that protection?
TIA,
Arnau
|