When you’re happy all these settings are correct, go ahead and save this file and exit the pico.Ĭlose all shells and reopen a new shell. The logs and TMP directories should be, in my opinion, located in a folder on a volume ALL the machines are connected to and can SEE.
Copy this down and put this in the MASTER= are of the profile file. Making sure this the correct network interface from the pulldown menu above this = the IP address of your master computer. If you’re unsure what your master computer is called or its IP address go to the master computer, open Applications / Utilities / network Utility and in the first window there, there should be an IP Address(es) with a number like 192.168.1.23 after it. Now using the arrows to move the cursor around edit the lines to reflect your networked master computer. Once pico is open if you’re reading this from an internet page or a text editor you can select the above lines, apple+C to copy and select the shell window with pico to apple+v these lines AFTER the export PATH line in the file (use the arrows on your keyboard to get the cursor below that line). The profile file resides in the /etc folder, and we use pico to edit this file. To do this open a new shell window and do the following. These are:Įxport DRQUEUE_MASTER=Įxport DRQUEUE_LOGS=/Volumes//drqueue/logsĮxport DRQUEUE_TMP=/Volumes/drqueue/tmp Is drqueues X11 graphical user interface for submitting files for rendering and for activating and deactivating renderfarm nodes etc.īefore any of these can be setup we need to use pico to edit our global environment for the operating system to set some general paths etc for drqueue. These tell the master their current status, if they’re busy rendering, or ready to receive a file for rendering. Is used on each machine you wish to use for rendering. This is required to monitor / receive jobs / activate jobs etc etc without this running the farm is technically dead. conf files for both master and nf is short for configure and it’s in these files you setup how master and slave work. Of importance is also the /usr/local/drqueue/etc folder because this contains the. The bin area is short for binary (executable) and contains the files used to run drqueue man. Master, slave and drqueue man are all located in /usr/local/drqueue/bin If you wish to use this check the steps below to get this working.
AUTOMOUNTMAKER X11 INSTALL
Is a web based python server for people to use their browsers to connect to a working drqueue man install to see the current state of jobs etc.
DrKeewee:ĭrKeewee is not considered at this point a production tool, but more like a bigger example of the possibilities around the python bindings I’ll explain these quickly because it wasn’t obvious to me right away.
AUTOMOUNTMAKER X11 MAC
Shawns tutorial covers an NFS approach to mounting your network drives required for network rendering, we went with AutomountMaker and the standard afp mac volumes approach.ĪutomountMaker can be set to fire off it’s maps 5 seconds after a fresh login, for example, and automatically mount your networked server drive on each box. NOTE: Mounting drives etc on Mac usually with a default install of the OS you would need to manually remount all drives on restart.
0 kommentar(er)
