Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
Installation Instructions
Requirements for the base tools (no python bindings)
To build the software you'll need several tools being those mainly the
standard C and C++ compilers, the SCons tool version >= 0.98 (you'll
probably find it as a package in your distribution) and the gtk2
development headers (to build the GUI drqman).
* gcc/g++
* scons (depends on python)
* gtk2 development headers
* pkgconfig (usually related to gtk2-dev)
* Mac OS X: needs Macports to install many of the previously
mentioned as well as XCode (providing the compilers) and X11 to run
drqman. X11 you'll be able to find on your installation CD/DVD. XCode
is best to be downloaded from Apple's developers site.
Depending on your platform you there would be different ways to obtain
the packages:
* Mac OS X: XCode, Macports (scons,gtk2,pkgconfig), X11
* Linux: with different names in the various distributions all the
packages are already available
* Windos: Cygwin for most of the tools, the native gtk-glade
development package for windows, python for windows standard and the
pywin32 extensions (later on).
Always refer to your own documentation for instructions on how to
properly install every package.
Building the software
DrQueue uses scons for building (and later on installing)
To build the main DrQueue command line tools and the Gtk+
GUI drqman just type:
$ scons
Installing the binaries
For example:
$ scons PREFIX=/usr/local install
will install the drqueue tree into '/usr/local/drqueue'
You may also modify the file 'scons.conf' to change the
default values.
This command will create the directory structure explained in:
That would be (for that example):
Everyone with they're own contents.
Uninstalling the copied files
To clean the installed files:
$ scons install -c
Basic usage
All DrQueue binaries will be found into the directory (following the
example) '/usr/local/drqueue/bin' so you should add that to your PATH
as a way to make things easier to work from that point on.
Environment variables
(There is a small helper tool 'bin/' that will help
you writting a very basic default environment file to be customized)
There will be many ways of customizing the operation of DrQueue, but the
first and most simple way will be through your environment variables. In
particular, the two most important for DrQueue will be:
* DRQUEUE_ROOT=/usr/local/drqueue
That should be pointint to the base path of the previosly created
directory structure.
Containing the IP address or name of the computer that will be
acting as 'master' for the farm (refer to:
for a global overview of the process)
Having PATH,DRQUEUE_ROOT and DRQUEUE_MASTER set will allow you to run
the tools right away.
(Note to Mac OS users, due to the usage of shared memory on DrQueue some
boot parameters need to be changed manually on file /etc/rc and the
process is documented on .
I'd recommend to follow the 'easy way' as the others have failed with
some configurations)
The most simple test
To have the most simple farm (a single computer running both master and
slave locally) you would proceed in the following order:
* Open a terminal window and type "master" (if you'd like some extra
verbosity and checking what's going on type "master -l3 -o" instead)
* Open a new terminal window and type "slave" (same logic applies)
* Having your X11 configured properly (that includes having set the
DISPLAY environment variable) you can then run "drqman"
With those basic three tools you will be then able to create jobs or any
other much more complex setup you might require.
Python (brief)
The python module uses Setuptools and SWIG to be built and installed
into the system (again check your documentation on how to obtain those
packages for your system).
Having all the former already working and installed the usual way to
build the bindings and install them woulbe:
$ cd python
$ sudo python install
(You need sudo because the Python module usually gets installed into
your standard Python site-packages directory which will probably need
super-user privileges to install files on it)
Check Setuptools documentation on how to make a local user module
Windows notes
You can build the python bindings using cygwin python tools, but then
(at least on my tests) the module won't work when using the standard
native version of python.
We are working on solving this problem.
Extra Notes
The daemons will spawn several processes each, that's normal (but can be
changed). And you can close the windows where you started the processes
without fear about stopping them, they'll keep on running even without a
The daemons react properly to the usual interrupt or termination
signals, so there's no especial way to stop the damons other that:
* If you have the terminal running, just click ctrl+C
* if that fails or you have no terminall you can use the command
"killall" with both executable names (short and long) like:
$ killall master
$ killall master.Linux.i386 (this last name will change for every
different operating system and architecture combination)
That naming convention, having a single wrapper script named "master"
(or whatever the tool is) that will then try to call the proper binary,
is thought so you can have your drqueue installation shared over the
network and every single computer will load the proper binary while the
directory is in fact holding all of them.