Rush Mac Install Instructions
(C) Copyright 1995,2003 Greg Ercolano. All rights reserved.
V 102.40g 05/06/03


	Mac OSX Install Instructions


	Installing Rush

1) Choose a local directory to install rush.

/usr/local/rush is recommended.

Open a terminal window, and login as root, and extract the tar file as:

Extracting Rush Tar File
cd /usr/local gunzip -c /tmp/rush-xxxxx.tar.gz \| tar xvfp -

Note the importance of the tar 'p' flag, to preserve permissions.

To install the system on a large network, first install the software on the license server(s), get everything working, then rcp(1) the directory tree to all the other machines on your network.

If you install rush in another location, then you must be sure the $RUSH_DIR environment variable points to the directory, and this variable must be set a) before the daemon is started and b) in all user environments. You will make life easier if you install rush in /usr/local/rush.

As with all daemons and their config files, do *not* install the rush directory or binaries on an NFS mounted drive. Keep rush binaries local to each machine.

2) Configure the /usr/local/rush/etc/hosts file

It should contain the names of all hosts that participate in rendering. See Hosts File for descriptions of each field.

3) (OPTIONAL) Configure the

/usr/local/rush/etc/rush.conf file.

For most situations the defaults suffice.

If you have a mixture of Windows and Mac machines, be sure to configure the ntrushuid and ntrushgid values.

You should register your settings for serverport in /etc/services, or equivalent; the docs include an example entry.

If security is an issue at your site, be sure to check ALL settings, esp. UidRange GidRange, Permit and WebUser for your environment. Read about them before accepting the defaults.

If you want to make changes, see the Rush Configuration File documentation for more info.

4) (OPTIONAL) Configure the /usr/local/rush/etc/templates file.

Customize the template render/submit scripts for your local environment. TDs use these templates to create their submit scripts and render scripts via 'rush -tss/-trs', and they will want to inherit settings for typical situations.

5) (OPTIONAL) 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 Scripts respectively.

6) Run the install script.

	/usr/local/rush/etc/bin/install.sh

7) Start the daemon, and test it

Start the daemon by invoking the boot script:

/System/Library/StartupItems/Rush/Rush start

UPDATE -- OSX 10.2 users: if you get an error 'RUSHSERVER: unbound variable', then edit the /etc/hostconfig and add a line that reads 'RUSHSERVER=-YES-', then re-execute the above daemon start script.

Then ping the daemon to see if it's running:


     % set path = ( /usr/local/rush/bin $path )
     % rush -ping
     imac: RUSHD 102.31h PID=7166    Boot=10/15/00,03:25:49  Online, 0 jobs, 0 procs

If you get an error:

% rush -ping +any rodin: rush: rresvport(): Permission denied bacon: rush: rresvport(): Permission denied

..then check the SUID bit on the rush(1) binary, and make sure the owner is root:


     chmod 4755 /usr/local/rush/bin/rush
     chown 0.0  /usr/local/rush/bin/rush

If you get a different error, check the daemon logs for problems, eg:


     tail -f /usr/local/rush/var/rushd.log

To test if the daemon is working, you can run this test submit script, just to verify jobs can be started, listed, and dumped:

/usr/local/rush/examples/test-submit

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.

8) (OPTIONAL) Setup accounting log rotations.


	 0 0 * * * root /bin/mv /usr/local/rush/var/cpu.acct /usr/local/rush/var/Ocpu.acct

9) (OPTIONAL) Security issues.

Refer to the

Admin FAQ on Security

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..

Network Install

To install rush on the rest of the network (assuming you've got it working on one machine), you will want to rcp(1) the /usr/local/rush directory to all the machines, start the daemons, and verify they're running. FIRST, make sure *all* the hostnames you will be installing on are configured in the /usr/local/rush/etc/hosts file. Then, release everything to the net, and start the daemons:

Rush Network Install Commands

foreach i ( host1 host2 host3 .. ) echo --- $i rcp -rp /usr/local/rush ${i}:/usr/local/rush rsh $i /usr/local/rush/etc/bin/install.sh \; /System/Library/StartupItems/Rush/Rush start end

Now verify all the daemons have started.
rush -ping +any # pings all daemons in rush/etc/hosts

Installing www-rush

This step is optional.
If you want to use www-rush, the web interface to rush, make sure *one* of the rush machines is also running a web server (like Apache). You would only need to the following config on the web server.

1) Copy the www-rush perl script to the webserver's 'cgi-bin' directory.

cp /usr/local/rush/cgi-bin/www-rush /Library/WebServer/CGI-Executables

2) Install the www-rush documentation in the documentation directory.

cp -rp /usr/local/rush/html/www-rush /Library/WebServer/Documents

3) Test it by opening Netscape to the URL for the script.

http://yourserver.com/cgi-bin/www-rush
Make sure your server daemon is running, eg:
apachectl start

4) Customize the www-rush script's variables if need be

Usually the defaults work fine, but sometimes the variables at the top of the www-rush script will need to be modified to help it know about your web server's environment.