Setting up DRQUEUE OSX Tiger 10.4.10:

NOTE: Mounting drives etc on Mac usually with a default install of the OS you would need to manually remount all drives on restart. 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.
AutomountMaker 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.
AutomountMaker can be found ...
http://www.versiontracker.com/dyn/moreinfo/macosx/21383

DrQueue comes with the following:

I'll explain these quickly because it wasn't obvious to me right away.

DrKeewee:

DrKeewee is not considered at this point a production tool, but more like a bigger example of the possibilities around the python bindings

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. If you wish to use this check the steps below to get this working.
master, slave and drqueue man are all located in /usr/local/drqueue/bin
the bin area is short for binary (executable) and contains the files used to run drqueue man. Of importance is also the /usr/local/drqueue/etc folder because this contains the .conf files for both master and slave. .conf is short for configure and it's in these files you setup how master and slave work.

master:

is the renderfarm master. This is required to monitor / receive jobs / activate jobs etc etc without this running the farm is technically dead.

slave:

is used on each machine you wish to use for rendering. These tell the master their current status, if they're busy rendering, or ready to receive a file for rendering.

drqman:

is drqueues X11 graphical user interface for submitting files for rendering and for activating and deactivating renderfarm nodes etc.

Before 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 are:

export DRQUEUE_ROOT=/usr/local/drqueue
export DRQUEUE_MASTER=[IP or Name of master computer]
export DRQUEUE_LOGS=/Volumes/[servername]/drqueue/logs
export DRQUEUE_TMP=/Volumes/[servername]drqueue/tmp
export DISPLAY=:0

To do this open a new shell window and do the following.
$  cd /etc
$ sudo pico profile

The profile file resides in the /etc folder, and we use pico to edit this file. 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). Now using the arrows to move the cursor around edit the lines to reflect your networked 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. Making sure this the correct network interface from the pulldown menu above this = the IP address of your master computer. Copy this down and put this in the MASTER= are of the profile file.

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.

When you're happy all these settings are correct, go ahead and save this file and exit the pico.

Close all shells and reopen a new shell. (By the way if you get sick of typing paths out to locations all the time I find a nice quick way to do this is to type the cd /usr stuff out and drag select the whole lot then drag that to the desktop. Every time I want to go to that folder in the shell I drag and drop that newly created file on the desktop to the shell and hit enter)

Setting up the master:

Time to edit the masters configuration file.

$ cd /usr/local/drqueue/etc
$ sudo pico master.conf

Edit these lines to reflect your drqueue install locations for db bin and etc (this should be /usr/local/drqueue/bin)

And the logs and tmp should be the same location as the profile location. This way we keep all our working logs and tmp in the same location for easy cleanup. Save this file and exit pico.
Mine ended up:

logs=/Volumes/Server/drqueue/logs
tmp=/Volumes/Server/drqueue/tmp
db=/usr/local/drqueue/db
bin=/usr/local/drqueue/bin
etc=/usr/local/drqueue/etc

Setting up the slave:

Remain in the above directory, or if you're not there type $ cd /usr/local/drqueue/etc

$ sudo pico slave.conf

Same as above for the master tmp and logs
Mined ended up:
logs=/Volumes/Server/drqueue/logs
tmp=/Volumes/Server/drqueue/tmp
pool=Maya
pool=MR:Maya

A Pool is a group of machines to render to. You can set a farm up to have several different types of pools for priority rendering or for say a mayaBase render setup and a mayaMentalray setup.

drqman:

requires the X11 application to display.
X11 resides in your applications / utilites folder in finder. Go ahead and open that up now. Go back to the shell and in the /usr/local/drqueue/bin type ./drqman
If you have downloaded the xfree stuff by accident or it was unavoidable you should be able to check your Applications/Macports folder in finder for XDarwin to load up the X11 stuff instead.