Greg Ercolano wrote:
> eg. login to machine 'jobserver' as anton.blomberg,
Oops, forgot this is a windows machine.
Correction to the above: login to machine 'jobserver'
as *what ever user the rushd service is configured to run as*,
since that is the user rush will be running your command as,
and is the permission context that will be used to access the
file server.
BTW, I'm a little surprised that the UNC paths you're using
don't include a volume name. Normally UNC paths are of the format:
\\someserver\somevolume\xxx
but your path to the jobdone.py script seems to be missing a volume
name, which I think is not possible under windows.
Also, a typo in my last response:
> dir \\logserver\logs\rush\jobserver.709
> dir \\tools/jobdone.py
The frontslash in that last line should be a backslash, eg:
dir \\tools\jobdone.py
My guess is that's not a valid path, due to the missing volume name,
but since the log directory looks correct (\\logserver\logs\rush\..)
I would think the jobdonecommand.log would be created, and show an
error message from python about the script not being found.
However, if \\logserver\logs is not a valid UNC path on jobserver,
that would explain the absence of the jobdonecommand.log, and surely
there will be an error in the rushd.log about it.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|