Installing RUSHD.EXE as a service

INTRODUCTION
------------
    By configuring RUSHD.EXE as a service, the daemon can be
    configured to automatically come up when the machine reboots,
    and stays running even when people login and logout.

PREPARATION
-----------
    To install rushd as an NT service, you must have the 
    NT Resource Kit installed.

    -OR-

    Download these two necessary NT Resource Kit files:

	INSTSRV.EXE
	SRVANY.EXE

    ..and put them in C:\RUSH\BIN. Be sure to add C:\RUSH\BIN 
    to your system path, so that they can be executed from DOS.

CONFIGURING RUSH AS A SERVICE
-----------------------------
    What follows are the instructions for using SRVANY.EXE and
    INSTSRV.EXE to setup rushd as a service.

    These are basically rush specific steps based on the 
    SRVANY documentation.

    Be sure to type data in carefully; you know how scary the
    registry can be.

	1) Login as administrator, invoke a DOS shell, and run:

		INSTSRV rushd C:\RUSH\BIN\SRVANY.EXE

	2) Invoke the registry editor, eg:

		REGEDT32

	3) In the HKEY_LOCAL_MACHINE window, descend into the 
	   following hierarchy:

	       System
		 |
		 --> CurrentControlSet
		      |
		      --> Services
			   |
			   |--> rushd

	4) With 'rushd' highlighted, in the regedit menu bar, invoke:

	       Edit -> Add Key

	   .. and in the window, type:

	       Parameters

	   This should create a new 'key' in the 'rushd' hierarchy.

	5) Click on "Parameters" to highlight it, then in the regedit
	   menu bar, invoke:

	       Edit -> Add Value

	   .. and in the window, type:

	       Application

	   .. and hit Return. In the "String Editor" window, type:

	       C:\RUSH\BIN\RUSHD.EXE

    You should now be able to go into the control panel's Services,
    and start the rushd service, eg:

	Start -> Settings -> Control Panel -> Services -> rushd

    .. and click Start. The file C:\RUSH\VAR\RUSH.LOG will start
    growing with output from the daemon. Monitor this file for 
    daemon error messages.

    To verify the daemon is running, type at a DOS prompt:

	rush -ping

    ..you should see a response, such as:

	mymachine: RUSHD 101.70 PID=67      Boot=05/23/00,13:45:32  Online, 0 jobs, 0 procs

    NOTE: Supposedly you can distribute the REGEDT32 changes you've 
    made to other machines easily. See your system documentation on 
    REGEDT32 for more info.

NT/UNIX CAVEATS
    If you have a mixture of unix and NT machines, be sure:

	o Your unix machines have a valid user called 'ntuser'

	o The uid/gid for this user is configured in the C:\RUSH\ETC\RUSH.CONF
	  file for ntrushuid and ntrushgid

        o Both Unix and NT machines have the same 'rush hosts' files, 
	  eg. C:\RUSH\ETC\HOSTS is the same as /usr/local/rush/etc/hosts

	o Both Unix and NT machines can resolve each other's hostnames, 
	  eg. you can 'ping' nt machines from unix, and vice versa.