- 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.
- Install 'Active Perl' for Windows from
http://www.activestate.com/
You can download Perl for Windows *free* from
http://www.activestate.com/.
The rush submit scripts are written in Perl, so unless you intend to
write all your own submit scripts in some other language, you'll need
to install perl.
- Unzip the rush distribution to C:\RUSH
- Edit the C:\RUSH\ETC\HOSTS file.
Edit the C:\RUSH\ETC\HOSTS file..
Create an entry for all hosts you'll be using for Rush.
Remove the example entries (amber, bart..).
- Install the license that was emailed to you as C:\RUSH\ETC\LICENSE.DAT
- Make sure the Windows Firewall is disabled.
Microsoft includes a firewall that is default 'on' in some
versions of Windows which, if left enabled, will prevent Rush
from being able to communicate with remote machines.
Disable the radio button in the 'Internet Connection firewall', eg:
Control Panel | Network | Lan | Properties | Advanced | Internet connection firewall
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.
- Run the following commands in DOS to install the daemon.
Windows7: If you are using Windows Vista or up, you may find it necessary to first
turn off the UAC,
or the install script may fail with "access denied" errors even when running as Administrator.
Note: You will *NOT* need to reboot after installation.
If you see errors about 'unrecognized command or batch file',
you probably have
this problem.
- Configure the 'Rushd' service Username and Password.
If you have Windows XP, you can just do:
sc config rushd obj= DOMAIN\USER password= PASS
net start rushd
Notes on the above:
- Replace DOMAIN\USER with the username you want the Rushd service to run as.
- Replace PASS with the password for the account.
- The domain name is required even if it's a Workgroup user.
If it's a Workgroup user, use '.' in place of the domain name, e.g. ".\render"
If it's a Domain user, use the actual domain name, e.g. "YOURDOMAIN\render"
- Microsoft's 'SC' command is unusual; the '=' characters are each followed by a space.
- Make sure the account has access to the file server with a
non-blank, non-expiring password. As of this writing, the SC command
does not support configuring password expiration, in which case do this
through the GUI.
If you don't have Windows XP, you'll need to do the following
steps (a) through (d) manually:
- Bring up services:
WIN/NT:
Start -> Control Panel -> Services
WIN/2K:
Start -> Control Panel ->
Adminsitrative Tools -> Services
- Double click the new 'Rushd' service.
- Set up the account the Rushd service will run as.
As of version 102.42 and up, you can set up the Rush service to run
as any user you want, including non-administrator users.
|
DOMAIN Users
|
If you have a Windows DOMAIN, it is recommended you create a
'rush' account in that domain:
a) The user should have an actual (non-blank) password.
b) The password is set to never expire.
c) Configure the Rushd service to run as that user.
|
|
WORKGROUP Users
|
If you have a Windows WORKGROUP, it is recommended you create a
local 'rush' account on each machine which:
a) Has a non-blank password.
b) The password is set to never expire.
c) Configure the Rushd service to run as that user (below).
|
Click 'This Account', configure login (Under Win2K + XP
you'll need to click the 'LogOn' tab)
WORKGROUP WINDOWS DOMAIN USER
--------------------------- ---------------------------
This Account: rush This Account: DOMAIN\rush
Password: <PASSWORD> Password: <PASSWORD>
Confirm: <PASSWORD> Confirm: <PASSWORD>
(Replace DOMAIN with your Windows domain name)
- Highlight 'Rushd' and hit 'Start'.
This starts the daemon, and enables it to start on reboot.
- Verify things are working.
Open a new DOS window and type:
If you get any errors, see troubleshooting.
- Install the submit scripts for the users
Use these instructions to
install the submit scripts on your file server.
Then login as a normal user, and verify you can
make
desktop shortcuts to the submit scripts, and can bring
up the interfaces properly.
- Handle cross platform configuration issues.
If you have a mixture of UNIX and WINDOWS machines,
see the UNIX CAVEATS below.
- Security Issues
If you're in an environment where security is an issue, then it is
advised you enforce the desired read/write permissions on the
c:\rush directory, specifically:
- The following directories and all files in them must be
writable by the user the Rushd service is running as:
- Only the following file needs to be writable by 'everyone':
-
Verify rush is running.
You can optionally run this test submit script, just
to verify jobs can be started, listed, and dumped:
c:\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.
-
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..
Possible error messages in the C:\RUSH\VAR\RUSHD.LOG
o "HOST_GetLocalHostname(): NO LOCAL HOST --- ABORT ---"
This means the local hostname for the machine is not in the