Anton Blomberg wrote:
> I'm trying to use the -jobdonecommand to execute a python script when a rush
> job is done.
> There is no problem with the submit or rendering, but the jobdonecommand is
> never executed.
> I set it to:
> jobdonecommand python //server01/jobdone.py
Hi Anton,
If you're using one of the submit scripts, and are using
the "Job Done Command:" prompt, then you would just type at
the prompt:
python /path/to/your/jobdone.py
(ie. without typing 'jobdonecommand')
When the last frame finishes rendering, that command
will be executed, and the stdout/stderr of the command
will appear in a file called 'jobdonecommand.log' in the
log directory for your job.
You would only specify the 'jobdonecommand' as part of the
command *if* you are supplying this in the 'Submit Options:'
prompt of the submit form (where you can insert any submit
commands), or if you are writing your own submit script,
and are doing all the submit commands yourself, eg:
rush -submit << EOF
title YOUR_JOB
frames 1-10
command python /path/to/your/command.py -arg1 -arg2
jobdonecommand python /path/to/your/jobdone.py
EOF
If you are still having trouble, supply more details
about which prompt you're filling out, and include
the contents of 'rush -ljf' and 'rush -lf' for your job,
the directory contents of your log directory, and if
there is one, the contents of the 'jobdonecommand.log'
file.
> but that script never runs. And no errors about it is logged.
> Are there any parameters that can interfere with the jobdonecommand that I
> need to set to enable/disable it?
There shouldn't be anything else you should need to set.
Let me know how it goes by following up on the group.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|