Installing Rush

	0) Verify your network is configured correctly before installing Rush. There are certain pre-requisites for Rush to ensure it can properly operate on your network. 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 - The tar 'p' flag is important! It will preserve the permissions needed to make the daemons run properly. To install Rush on a large network, first complete all the steps to install on one machine, then use the Network Install instructions to install on all the rest of the network. If you want to install rush in another location, refer to these instructions. WARNING: Do NOT install Rush on an NFS drive. Here is why. 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) Install the license that was emailed to you into /usr/local/rush/etc/license.dat. 4) Security issues and special configurations. If security is a concern at your site, carefully review the Admin FAQ on Security for security precautions and configuration. (OPTIONAL) Review the /usr/local/rush/etc/rush.conf file. For most situations the defaults suffice, but sometimes it pays to be pedantic. (OPTIONAL) Register your settings for serverport in /etc/services or equivalent (NIS, NetInfo, etc). See serverport for an example services entry. 5) Run the install script. /usr/local/rush/etc/bin/install.sh 6) 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 -t 5 rodin: rush: rresvport(): Permission denied bacon: rush: rresvport(): Permission denied ..then you probably forgot the tar 'p' flag when you extracted the software in step #1! Set the permissions manually on the rush and rushd files: chmod 4755 /usr/local/rush/bin/{rush,rushd} chown 0:0 /usr/local/rush/bin/{rush,rushd} 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. 7) Install the submit scripts for the users There is a special version of the submit scripts for the Macs so that people can click on them from their desktops. As root: make a directory on your file server called 'rushscripts' as root, and copy the entire /usr/local/rush/examples/Applications directory to it, e.g.: mkdir -m 755 //server/volume/rushscripts cp -rp /usr/local/rush/examples/Applications //server/volume/rushscripts/Applications Then login as a normal user, and verify you can Make Mac Desktop Shortcuts to the Submit Scripts, and can bring up the interfaces properly. 8) (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 submit/render scripts. 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. 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. 9) That's it. Once you have things working on the first machine, then you can easily install rush on the rest of the machines using the Network Install instructions 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 already configured in the /usr/local/rush/etc/hosts file. This implies the new machines being added are already in DNS (or whatever system you're using for mananging hostname lookups). ALSO, on the new machines being configured, make sure you disable any software firewalls that might prevent rush from communicating before installing Rush. Then, copy the entire /usr/local/rush directory to the rest of the machines and start the daemons with these commands: 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 rsh $i /System/Library/StartupItems/Rush/Rush start end Now verify all the daemons have started. rush -ping +any -t 5 # 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.