Mac Systems Administrators: Making Scripts Available To Users

The goal is to copy the rush submit scripts onto a file server so that:

1. Users can access the scripts to make shortcuts onto their desktops
2. A directory that all the render machines can access

The submit scripts *must* be placed on a file server all workstations and rendering machines can access. The submit scripts not only bring up the GUI, but also handle rendering frames on render hosts, so the render machines must be able to access them.

Making desktop shortcuts is only available in Rush 102.40f and up. For older releases (pre-102.40f), you have to invoke submit scripts from the terminal window, and need to use the more generic unix/windows setup instructions.

Copy the submit scripts to your file server.

You can do this from the command line, eg:

     cp -rp /usr/local/rush/examples //yourserver/jobs/rushscripts
     chmod -R a+rx //yourserver/jobs/rushscripts
     

Or, if you don't like the command line, you can do this from the Mac Finder using these instructions. However, the command line is probably quicker, and gives you more control of permissions.

Login as a normal user and verify users can follow these instructions.

You should verify users can follow those instructions to create Desktop aliases, and successfully start renders with them.

Submit a test job.

It's important to verify the submit scripts can invoke themselves over the network. A very simple verification test would be:



A simple test using submit-generic.

You may also want to test the other render scripts, to ensure the 3rd party renderers are accessable to the submit script.

Sometimes environment variables and path settings need to be added to the submit scripts to ensure they can invoke the renderer correctly.

Since you have a copy of the scripts on your file server, you only need to edit the one copy there, and all the machines will see the change right away.

That's it.