WOW that was a pain!!  I'd better write down how to do this as quickly as possible before I forget.

In short:  I'm configuring a networked render farm for my computer lab at FAU, as well as, replicating the system at home.  Dr Queue, of course, will be the render manager of choice.  I am, after all, "the open source guy".  I'm primarily working in a Linux/Mac environment. So, file sharing will be done with NFS at this point.  Once I need to introduce Windows into the mix, I"ll figure that one out.  

So, here it is, in the fewest words possible.  Installing Dr. Queue, the overview.

You can configure your environment before or after you compile and install Dr Queue, so let's compile now.  Pre-compiled binaries end up in really weird places in your computer.. I've installed them,, believe me.  But, then they are never found again.. 

I'm using Ubuntu Linux and apt to compile Dr. Queue

# make the directory you'll be compiling out of,  I use a src folder in my home directory

mkdir ~/src
cd ~/src

# grab all of the stuff you'll need from apt

sudo apt-get install build-essential scons
sudo apt-get build-dep drqueue

# compile and install.  PREFIX=/ will install your binaries into /usr/local/drqueue

scons
scons PREFIX=/ install

Congratulaitons, you've successfully compiled and installed Dr Queue in Linux, which is considerably easier to do than on the Mac.  Now lets work out some of the details of the configuration.  JOY! 

Configuration:

#We need to add the correct environment variables. 

 sudo vim ~.bashrc 

#add

PATH=/usr/local/drqueue/bin:"${PATH}"                  #this appends the path to your compiled binaries for drqueue to the existing ${PATH}
export DRQUEUE_ROOT=/usr/local/drqueue/bin      #where drqman lives
export DRQUEUE_MASTER=192.168.0.101             #the ip where you're running master.

Okay, at this point you have a working installation of Dr Queue!  To run, open a terminal and type "master". Then, I right click and open a new tab and run "slave".  Finally, open another tab and run drqman.  Check the "Computers" tab in drqman, there you should see your computer staring back at you in all of it's potential computing goodness.

drqman running in ubuntu linux

Weeeeewww.. grab a caffinated beverage folks.. we're moving onto the Mac! Dr Queue on the Mac is a considerable pain in the ars.

Configuration and Compilation all tied up in one knarly mash of crap:

#go ahead and edit /etc/profile  

sudo vim /etc/profile 

# Add ...

PATH="/usr/local/drqueue/bin:/opt/local/bin:"${PATH}

# Now if you pull up a terminal and type echo $PATH you should get

Macintosh:~ snovak$ echo $PATH
/usr/local/drqueue/bin:/opt/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin

Okay,, I decided to cheese out.  I wound up downloading the binaries for the Mac .  Here's my very valid reason:  Ready? ...  ports was having some issues finding one of the dependancies when I was trying to install gtk2.  The install kept failing.. And, I am inherently impatient about these things.. So,, ONWARD!

# move the downloaded gz file to /usr

sudo mv ~/Desktop/DrQueue.0.63.1h.usr.local.tar.gz /usr
cd /usr

# extract the package

sudo tar -xvfz DrQueue.0.63.1h.usr.local.tar.gz

# Just make sure that your path is still valid.

sudo vim /etc/profile 

# Change our previous changes (PATH="/usr/local/drqueue/bin:/opt/local/bin:"${PATH}) to ....

# Note: drqueue.0.62.0 should be  what ever dir is in YOUR /usr
PATH="/usr/local/drqueue.0.62.0/bin:/opt/local/bin:"${PATH}

# I kept getting an error message pretaining to the tmp and db directories.. It turns out, by default, it's linked to some silo directory..  just recreate the directories.

$ rm tmp
$ mkdir tmp
$ rm db
$ mkdir db