This tar-file contains the sources of the server part of 
System Configuration Collector.

It can be used to install the software by means of the command:

	./scc-srv-install

It can also be used to customize the software before packaging it.
The packaging can be done with the following programs (in alphabetical order):

	- debian-gen-scc-srv		DEB for Debian
	- dragonflybsd-gen-scc-srv	TGZ for DragonFlyBSD
	- freebsd-gen-scc-srv		TGZ for FreeBSD
	- hpux-gen-scc-srv		SD-UX format for HP-UX
	- netbsd-gen-scc-srv		TGZ for NetBSD
	- openbsd-gen-scc-srv		TGZ for OpenBSD
	- pacman-gen-scc-srv		.pkg.tar.gz for ArchLinux
	- pisi-gen-scc-srv		pisi for Pardus
	- puppy-gen-scc-srv		PET for PuppyLinux
	- rpm-gen-scc-srv		RPM
	- slackware-gen-scc-srv		TGZ for Slackware
	- src-gen-scc-srv		source format
	- sunos-gen-scc-srv		package format for Solaris
	- ttylinux-gen-scc-srv		TBZ for ttylinux

These commands should be used in the current directory. The resulting 
package, rpm, depot or tgz-file is located in the current directory.
Other files and subdirectories are removed.

To install scc-srv in non-default directories you have to untar the
source tarball, edit the script relocate, run it, followed by src-gen-scc-srv.
This produces a new source tarball that can be used to produce a depot,
rpm or packages.

The following list summarizes the steps to get scc-srv working.
We assume that SCC-data is transferred via email and that it is 
referenced by a symbolic link from the document root of the web server.
Refer to the remainder of scc-srv.5 for a more detailled description 
and other setups.

1  activate the web server and email-processing
2  install scc-srv
3  extend the mail-alias file:
      scc-transfer:	"| /opt/scc-srv/bin/scc-receive-mail"
4  activate the new alias:
      newaliases
5  determine the user and group used by during the email delivery
   and assign the proper ownership (assume mail:mail):
      scc-update -m mail:mail
5  determine the user of the webserver assign the proper ownership
   (assume http):
      scc-update -w http
6  put the SCC-data in applications/scc under the document root:
      mkdir <doc-root>/applications
      ln -s /var/opt/scc-srv/data/www <doc-root>/applications/scc
7  indicate this path to scc-srv:
      scc-update -d /applications/scc
8  schedule scc-update to process incoming SCC-data, frequency depends
   upon the amount of data and time of arrival of new SCC-data.
      scc-update	# no arguments/options required

When you have password-less access to your clients, you can use
scc-pull to pull the scc-files from the clients.
