I'll let you know what I find next time it occurs. It seems to only happen with jobs running on a specific group of machines that are being used for GPU-accelerated rendering.
On May 4, 2012, at 12:35 PM, Greg Ercolano wrote:
[posted to rush.general]
On 05/04/12 12:16, Mr. Daniel Browne wrote:
> I'm executing using your=20
> (exitcode, errmsg) =3D Rush.RunCommand(command)
> call, version 82
OK, then I'll need that other info; (1), (2), (2a), (2b)..
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures
dbrowne@(email surpressed)
Office: (415) 777-0666 x105
|