Saker Klippsten wrote:
> I to would like to get cleaner working :)
I think it's hit a wall with the 'run as a service' thing,
where he replicated the hang from a DOS command line using
telnet, and is going to report it as a bug to Autodesk.
You can *probably* get past this hanging problem by, instead
of running rushd as a service on the windows machines,
running it from a DOS prompt (so that the renders have access to the desktop).
That's sucky though to do for an entire farm, because logging
out will kill rushd when configured this way, and it would mean
you'd have to leave all the nodes logged in with rushd running
in a DOS window, which is silly, and is an UGLY workaround.
But if you do it only on one dedicated box, maybe it's worth it
to specially configure rush on that one box to run from DOS.
There's a description of how to configure Rushd to run from DOS
instead of as a service here:
http://www.seriss.com/rush-current/issues-afterfx-7.0/index.html#DualProc
The real problem here is the Cleaner command line tool is actually
trying to use the desktop, which is bad for any kind of command line
based tool intended for distributed rendering. The vendor, Autodesk,
needs to fix that. (And the spaces in the Cleaner's executable name,
and the frontslash argument stuff would be secondary, but also important..)
|