Here are the instructions for installing SENDS (Scalable Enterprise Network
Directory Services).

0) Uncompress and extract the tar file (or unshar the shar file).

1) Create a directory for the root of the installation (TOP_DIR) e.g.

	mkdir /usr/local/sends

   or

	mkdir /usr/adm/sends

2) Edit the Makefile to make the TOP_DIR variable reflect that directory.

3) Edit the Makefile in the 'man' subdirectory and change the value for
   MANROOT if needed. This is where the man pages will be installed.

4) Run 

	make install

5) Create the data directories. A sample tree will be found under the data
   directory in this kit. The data tree needs to be rooted at TOP_DIR/data.

6) create a sends.conf file in the TOP_DIR/data directory.

   look in the sample data directory under the source directory for a
   sample. Theres a man page on the format too.

7) create one or more domain directories under TOP_DIR/data and groups in
   there look at the sample data tree for examples.

   e.g. data/lisa.usenix.org

	- directories not starting with a lower-case letter are
	  ignored during operation--useful during setup.

8) foreach group within the domain create a subdirectory (inside the domain
   directory).

   Again directories not starting with a lowercase letter are ignored by
   the code.

   e.g. data/lisa.usenix.org/us
	data/lisa.usenix.org/them

9) Foreach group directory created in step 6 you must create the following
   subdirectories:

	bad
	work
	output
	ftp

10) Put a 'control' file in the group directory following the example from
    the supplied data tree and the man page.

11) Create an ftp account for each group and make its home directory be the
    'ftp' subdirectory as.

12) Put a 'host' and/or 'users' in the 'ftp' directories for testing.

13) run the script 'TOP_DIR/bin/cronrun.often' to test. The results will 
    be under

	TOP_DIR/data/Users
	TOP_DIR/data/Zones

    (mostly in the 'output' directories).

The scripts use the various 'work' subdirectories as staging areas. When a
new host or users file for a group is deposited in the ftp directory it is
compared against the previous one--the one in the 'output' subdirectory. If
they're the same, nothing is done. So to really test things completely
you'll need to remove the hosts/users files from the output subdirectories
(under the Users, Zones and group directories).

When you're happy with the setup and testing. 

14) Go to the top of your DNS data tree add a symlink:

	ln -s TOP_DIR/data/Zones/output sends

15) To your named.boot file add the appropriate 'include' statement to
    include the 'boot.primary' file in TOP_DIR/data/Zones

16) distribute the boot.secondary in the same directory to your
    secondaries.

Both the boot files will change as you add zones so automating # 16 will be
helpful.

17) Put a crontab entry to run TOP_DIR/bin/cronrun.often. The frequency
    will depend on how much your network changes. The code doesn't
    regenerate files if nothing changes so you can afford to run it quite
    often (like every half hour).

18) Give out the ftp account details to each group and explain how things
    work. Which are:

	- they 'put' a 'host' or 'users' file in their ftp directory whenever
	  hosts or people change.

	- The file is moved and processed. If it meets the appropriate
	  requirements (see below) new master data files will be regenerated.

	- mail will be sent notifying of success or failure.


set up some form of auto distribution of secondary files and mailer
        databases.
