Dylan Penhale wrote:
Thanks Greg, this is the first time I have seen this happen, and only
because we write the frame sizes out to job notes so the uses can tell if a
frame wrote correctly. Also if a none standard frame size in encountered
automatically re-queue the frame, never host that CPU, and mail an alert.
In one case though a batch job of 360 frames (!) was submitted that output
every frame size to an array and then output that lot to the job notes. Not
sure how many characters, but certainly more than 1000. We have changed the
code here now to stop that happening, so it's not an issue for us, but I
thought it was interesting.
A frame note that long is not really what was intended when we set it up :)
In the next maintenance release, I'll have the rush(1) command error out
if the notes for a frame or jobnotes is too long, to prevent problems.
It will print out the limit length as part of the error message.
I've also enlarged the limit.
This fix will be in 102.42a1
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|