[GE users] DRMAA output redirection oddness
reuti at staff.uni-marburg.de
Sun Dec 12 13:32:54 GMT 2010
Am 10.12.2010 um 23:04 schrieb Reuti:
> Am 08.12.2010 um 13:10 schrieb epistemyscott:
>> On 7 Dec 2010, at 19:19, reuti wrote:
>>> Am 07.12.2010 um 15:29 schrieb epistemyscott:
>>>> The DRMAA bindings get upset if the output path doesn't start with a ':'. The official format in the Javadoc is "[hostname]:file_path", although I'm not specifying any hostname - I presume this means "leave things as they are", though I may be wrong - I couldn't find any explicit explanation of what happens if you don't specify a host name.
>>> What about using a native specification and -o/-e/-wd for now, are the pseudo variables working there?
>> The stuff I'm writing has to work with TORQUE as well (hence the DRMAA), so I'd like to stay away from native specs as much as possible. Nonetheless, I gave this a try, and it doesn't work - using job.setNativeSpecification("-wd ~/SGE-test -o SGE-test.log -e SGE-test.err.log"); and removing the DRMAA lines fails with the familiar message:
>> 12/08/2010 11:54:28|worker|host123|W|job 92.1 failed on host host123.epistemy.com general changing into working directory because: 12/08/2010 11:54:27 [1024:14268]: error: can't chdir to /SGE-test: No such file or directory
Did you also observer, that "job.setWorkingDirectory" will create the target directory, when it's not present?
Is this a feature or a bug? The plain `qsub -wd <directory>` will send the job into error state instead, which is what I expect. Though the DRMAA specification could be different.
To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].
More information about the gridengine-users