Trouble with Render Jobs As User

Deadline
1

I’m trying to set our linux-based facility up to use the Render Jobs As User option, but not having much luck with it. I’m launching my slave process as root, and everything starts out just fine. But then at some point the render writes a file to my /tmp/ directory that is owned by root instead of the user that the render is running under. The user then can’t open the file, so the render fails.

Has anyone come across this? Any ideas on how to track down why a temp file is being written as root?

Thanks!

2

Hello,

I do believe this is a known issue, and the currently advised work around is to change the local data path to something accessible by all users.

3

Thanks, I’ll give that a shot. Just to make sure I’m understanding correctly, the workaround is to create a directory like /tmp/render_data which I give all users access to, and then use the auto configuration to set that to the local data path. Does that sound right? And then all of the local data will be written directly into that directory, rather than in a job-specific subdirectory under that path?

4

That is correct. If you can set the umask so that files created use open permissions, that would be great too.

5

Looks like that didn’t work - despite setting the default access control list for the volume that the temp data lives on, the files created by root are still being created with closed permissions. And we don’t want to set the policy for all files owned by root to be wide open, for obvious reasons. :slight_smile:

Is there anywhere in the repository code where I could modify the code that’s run to create the temp files or directories? I could either make it run as the user or just add a chmod in along with the file creation. Thanks for your help in tracking this down!

6

Hello,

So, it sounds like a lot of issues in this realm of Deadline’s features should be fixed with 7.2, but in the meantime could you email support@thinkboxsoftware.com and reference this forum post, as a coworker of mine has a few things he’d like to go over, and the best way to do that is via our support ticket system. Thanks.

7

Will do, thanks so much!