-------------------------
Common Installation Steps
-------------------------

Downloading and building the DNX server and client components require the
same set of steps, except that these steps should be done on different 
machines. The DNX Server should be downloaded, built, and installed on the 
Nagios system, and the DNX Client should be downloaded, built, and installed
on individual worker nodes.

Follow these common steps on the appropriate machines for both Server and
Client components:

1. Download the latest DNX source archive from http://dnx.sf.net/download
2. Unpack and change into the archive directory:

  $ tar xf dnx-0.20.tar.gz
  $ cd dnx-0.20

OR (if you're building from a Subversion work area):

1. Update your work area:

  $ svn update

2. Change into the dnx directory and run autoreconf (with the -i option
   to install missing autotools files - only the first time).

  $ cd dnx
  $ autoreconf -i

From here, the instructions are the same for both paths:

3. Configure and build:

  $ ./configure
    ...
  $ make (or make all)
    ...

-------------------------
Installing the DNX Server
-------------------------

The DNX server runs as either an integrated plugin/server or as a split
plugin/server. These instructions indicate how to install the split
plugin/server model. The plugin runs as a Nagios evnent broker plugin,
which is a small shared library that Nagios loads into its own process
address space as it starts up. The DNX server runs as a child process of
the Nagios process. The plugin library loads this process and establishes
an IPC channel to it, through which it communicates jobs to be executed.

(Begin with the common download and build instructions above.)

4. Install the server components (as root):

  $ su
  Password: ******
  # make install-plugin
  # make install-servercfg

5. Create the log directory and give nagios permission to access it:

  # cd /usr/local/nagios
  # mkdir var/log
  # chown nagios:nagios var/log

6. Configure Nagios to load the plugin module

  # echo "broker_module=/usr/local/nagios/lib/dnxPlugin.so \
  > /usr/local/nagios/etc/dnxServer.cfg" >> etc/nagios.cfg

7. Restart Nagios:

  # service nagios restart
    ...
  # exit
  $

NOTE: These instructions assume you've used all the Nagios defaults to 
install Nagios. The DNX defaults assume the Nagios defaults. If you've 
installed Nagios into a different directory tree, or changed the Nagios
user and group names, you'll have to use appropriate configure options on
the DNX configure command line.

NOTE: Aspects of these instructions pertain specifically to opensuse
GNU/Linux systems. If you're running a different distro, you may have to
tweak the instructions related to starting services a bit.

-------------------------
Installing the DNX Client
-------------------------

Large Nagios installations will require more DNX client nodes to handle the 
workload that DNX manages for Nagios. Experimentation will show you how many
worker nodes are necessary for your shop. Start with one, and add more as
needed. Using the default DNX security model, no Server-side configuration is
required to add nodes. Simply install and configure them to talk to your DNX
server, and bring them up. They'll immediately begin requesting work from 
the DNX server. 

The DNX Client may be built from a source archive or from a Subversion 
repository work area. To build and install from a source tarball follow 
these instructions on a machine other than the one on which you are running 
Nagios:

(Begin with the common download and build instructions above.)

4. Create a user and group for the dnx client (as root):

  $ su
  Password: ******
  # groupadd dnx
  # useradd -G dnx dnx
  
5. Install the client components (as root):

  # make install-client
  # make install-clientcfg
  # make install-initscript

6. Create the log directory and give dnx permission to access it:

  # cd /usr/local/nagios
  # mkdir -p var/log
  # chown dnx:dnx var/log

7. Edit the dnxClient.cfg file to specify the server host address.
   For example, if I had installed DNX server onto a machine named
   "pluto" within my local domain, I'd make the following changes 
   to my dnxClient.cfg file:

   - channelDispatcher = udp://pluto:12480
   - channelCollector = udp://pluto:12481

8. Link the init script to your system init script directory, and configure
   the system to start the client at boot time:

  # ln -s /usr/local/nagios/etc/init.d/dnxcld /etc/init.d/dnxcld
  # chkconfig -a dnxcld
  # chkconfig dnxcld on

9. Now manually start the dnx client daemon:

  # service dnxcld start
  # exit
  $

As with the DNX server, configure supports options for changing the 
DNX user and group. Enter ./configure --help=short to see these options.

NOTE: Aspects of these instructions pertain specifically to opensuse
GNU/Linux systems. If you're running a different distro, you may have to
tweak the instructions related to installing and starting services a bit.

-----------------------------------------------------------------------------
  The following are generic instructions for using Autotools build systems.
-----------------------------------------------------------------------------

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.

   This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').

   It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring.  (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

   The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'.  You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  Run `./configure --help'
for details on some of the pertinent environment variables.

   You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment.  Here
is an example:

     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix

   *Note Defining Variables::, for more details.

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory.  After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on.  Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:

     CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

     OS KERNEL-OS

   See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.

   If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.

   If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Defining Variables
==================

   Variables not defined in a site shell script can be set in the
environment passed to `configure'.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'.  For example:

     ./configure CC=/usr/local2/bin/gcc

will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).

`configure' Invocation
======================

   `configure' recognizes the following options to control how it
operates.

`--help'
`-h'
     Print a summary of the options to `configure', and exit.

`--version'
`-V'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`--cache-file=FILE'
     Enable the cache: use and save the results of the tests in FILE,
     traditionally `config.cache'.  FILE defaults to `/dev/null' to
     disable caching.

`--config-cache'
`-C'
     Alias for `--cache-file=config.cache'.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`configure' also accepts some other, not widely useful, options.  Run
`configure --help' for more details.

