Here are some adminstration scripts and programs that may
or may not be useful. These are distributed 'as is'. Anyone
who uses these scripts and programs assumes all risk of their
use.

To install these, I would copy the admin.tgz file to /tmp
and run the following to install everything:

cd /etc; gunzip -c /tmp/admin.tgz | tar xpf -

The various scripts may or may not work in other places
without modifications. All of the scripts may need modifications
to fit specific environments.

nisupdate

The nisupdate script allows you to use find and modify the
system files in their normal places (i.e. /etc/hosts, /etc/passwd,
etc.) and use standard tools like vipw and admintool to modify
them, and propagate changes in these files into the NIS+ data base.
The data in the files resident on the NIS+ master host are used
to populate the NIS+ data base. A subdirectory in /etc/admin
maintains a shadow copy of the NIS+ data files.

This script can be run from cron and/or run manually whenever
any of the data files changes. The NIS+ databases will be
incrementally updated and pushed across the network.

You still need to set up NIS+ servers and clients in the
normal manner. Currently, if you change a password, you must
either change it in the shadow file on the NIS+ master and
run nisupdate or change it in both the shadow file and in
the NIS+ data base with nispasswd (or passwd -r nisplus). If
you only change it in the NIS+ data base, it may revert to the
old password the next time nisupdate is run.

For the auto mount maps, files called 'auto_master_global',
'auto_home_global' etc. are used for NIS+ automap maps. The
auto_master and auto_home files ordinarily contain just
+auto_master or +auto_home and may include host specific
maps. Three automount maps are defined, /home, /alt and
/alt1. Sample automount files are in the directory admin/auto.
Only the NIS+ master contains all of them in its /etc/directory.
NIS+ clients do not require the *_global versions.

pigs

This directory contains a script which is run from cron at
night and accumulates info about old or big files that are
cluttering up your disks. Resulting files are sorted by size.

clone_sys

This script is used to clone /, /usr and /var partitions
to another disk for backup and/or checkpoint purposes. I have
used this for cloning a system to a new motherboard/disk
combination, but some hand holding is required. Normally,
I reserve enough space on a second disk to duplicate all
of the major system files and create an alternate bootable
system for use in emergencies.

bup_xxx, incr_bup

These are primitive scripts are for backing data up to tape
and/or disk using ufsdump.

newsyslog

This is a alternate version of Sun's newsyslog script which
maintains a deeper history and keeps old logs compressed. This
can be run instead of /usr/lib/syslog from cron. Simply replace
/usr/lib/syslog in /var/cron/crontabs/root with /etc/admin/newsyslog.

                        bin/ftest
                        bin/fupdate
                        bin/src/ftest.c

This is a program which compares file dates for a number of
files and returns status about the relative modification times
of those files. It can also modify file dates to be any specified
amount of time ahead or behind the date of another file. See
the comments in ftest.c for its use. This is used by the
nisupdate script.

                        snooper
                        bin/snooplog
                        bin/src/snooplog.c
                        snoop_pat

Programs and scripts to filter snoop output and collect it
in a log.