- Be sure your network meets
these prerequisite requirements.
This is essential to ensure a stable network so Rush can operate reliably.
It's important machine's hostnames and IP addresses don't change after
casual reboots. IP addresses should be consistent through reboots,
which a well configured static DNS (or /etc/hosts) configuration provides.
- Make sure your
/etc/hostconfig file has a
This disables the unwanted 'hostname.local' Rendezvous/Bonjour stuff
that causes instability in production networks.
Example: if your machine is named "tahoe", then make the entry:
If the entry doesn't already exist, add it as a new line.
If there's an existing entry in the file that reads "HOSTNAME=-AUTOMATIC-",
replace it with the above. Do NOT put dashes around the hostname.
After making your changes, reboot.
There should *NOT* be a '.local' in your entry, as that's a special domain
that Mac uses for Rendezvous/Bonjours.. use some other domain name, if you
specify a domain name at all. Be careful when editing /etc/hostconfig:
- Use an ascii text editor
to ensure no font formatting characters get into the file.
- Don't make typo's! This file is parsed during boot.
- Extract the rush tar file.
Extract the tar file to /usr/local/rush.
Open a terminal window, and login as root, and extract the tar file as:
Extracting Rush Tar File
gunzip -c /tmp/rush-xxxxx.tar.gz | tar xvfp -
Some notes on extraction:
- Configure the /usr/local/rush/etc/hosts file.
It should contain the hostnames of all machines that will be rendering or submitting jobs,
in addition to the license server.
See Hosts File for a description of this file's format.
- Install the license that was emailed to you as
- Security issues and special configurations.
- Disable the OSX firewall.
Apple now includes a firewall that is default 'on' in some
versions of OSX which, if left enabled, will prevent Rush
from being able to communicate with remote machines.
Disable the the firewall via:
10.4 and older
(Tiger and older)
System Preferences > Sharing > Firewall > Stop
10.5 and newer
(Leopard, Snow Leopard..)
System Preferences > Security > Firewall > Stop
Or, if you want the firewall enabled, make sure TCP and UDP port 696
is left open in the 'Settings' menu. If you want Rush to be able
to send email on job completions, you'd better allow port 25 to be able
to reach your mail server as well.
- If security is a concern at your site, carefully review the
Admin FAQ on Security
for security precautions and configuration.
- (OPTIONAL) Review the
For most situations the defaults suffice, but sometimes it pays to be pedantic.
Register your settings for serverport
in /etc/services or equivalent (NIS, NetInfo, etc). See
for an example services entry.
- Run the install script.
Run the install script by typing:
Watch for any error messages in the output.
- Start the daemon, and test it.
Start the daemon by invoking the boot script:
Then open a *new terminal window* and invoke 'rush -ping' to verify the daemon's running:
Testing The Daemon
% rush -ping
yourhost: RUSHD 102.42 PID=XXXXX Boot=10/15/00,03:25:49 Online, 0 jobs, 0 procs
Some errors that may occur:
- can't open port lock file '/usr/local/rush/var/nextport': Permission denied
You either weren't running as root when you ran the install script,
or somehow skipped running the install script.
To fix this, be sure you are logged in as root, and re-run the install script.
- connection refused
This means the daemon wasn't able to start.
Look in the /usr/local/rush/var/rushd.log for error messages.
To test if the daemon is working, you can run the following test submit script
just to verify jobs can be started, listed, and dumped:
- Install the submit scripts for the users
If you haven't already installed the scripts on your server yet, follow these instructions
for installing the submit scripts on your file server:
'Making Scripts Available To Users'.
Once installed, users can make desktop shortcuts to the scripts by using these instructions:
'Making Desktop Shortcuts To Submit Scripts'
To submit a real job, similar to what TDs use, you can run
this test which includes
complete instructions for someone who has never used rush before.
- (OPTIONAL) Miscellaneous configurations
- Configure the /usr/local/rush/etc/templates file.
You can customize the output of 'rush -tss' and 'rush -trs',
useful for advanced users who want to quickly create their own
- Configure the /usr/local/rush/etc/.submit and /usr/local/rush/etc/.render files.
These files are sourced by the default Submit Script and Render
- Accounting log rotations.
Rush maintains a history of cpu utilization information in the
/usr/local/rush/var/cpu.acct file. If you don't want this
file to grow too large, you might want to have it rotated on a
monthly basis, eg:
0 0 1 * * root /bin/mv /usr/local/rush/var/cpu.acct /usr/local/rush/var/Ocpu.acct
You may want to then push the rotated file through an accounting filter
to keep tabs on cpu usage for the network. This is left as an exercise
to the reader.
- That's it.
Once you have things working on the first machine, then you can easily
install Rush on the rest of the machines. See 'Network Install' below..