Hello: We are using Nuke 8 in linux and I'm noticing a lot of .tmp files being left behind on jobs that get interrupted. So, say Nuke is rendering and a higher priority job comes along and sends a SIGINT to it, nuke quits but leaves behind the .tmp file it was writing. On shows that used version 7 I don't really see any of these .tmp files. Was there something changed in the way Nuke handles interrupts/signals? Is there a better signal to send to Nuke to have it quit more gracefully and delete the .tmp file it was working on? Unfortunately, we can't use Nuke 9 just yet, so hopefully looking for a solution for Nuke 8 that also won't have me writing a script to clean out the .tmp files when a job is done. Or, can I maybe tell nuke to write to a temp space and then move the finished frame to the network?
Thanks! Jake -- -- -------------------------------------------- [email protected] 203-992-6319 LTD Blue Sky Studios --------------------------------------------
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
