Statistics server's are greatly simplified when compared to the monitoring server. No database support is required, and the configuration files themselves, as you'll soon see, are nearly identical for all statistics servers on the network. All that is really required is that you compile, install, and ensure connections can be made to the service from your monitoring server. Download and unpack the State source code and configure it like so:

$ ./configure --enable-pvd-only
    

This will instruct State to only build pieces necessary for a statistics server and to ignore other more monitoring specific parts. No web related executables will be compiled and linked either, only the essentials. If you need to fullfill any dependencies, libxml for example, then go ahead and do that and come back to this step. Follow this step up, if everything goes well, with the standard autoconf installation procedure:

$ make
$ make install
    

Now you'll need to make State available to the outside world. There are two popular ways of doing this. You can setup State to run as a daemon, which means it'll always be running. Or, you can run State from an INET type super server, which is the preferred solution. State, by default, is designed to run using the ucspi-tcp package available at http://cr.yp.to/ucspi-tcp.html, but should operate with any other similar solution. All you really need to do is ensure that runpvd.sh is executed when your machine starts up, and everything should go as planned. You can, optionally, install the SysV startup scripts to make managing the server easier and standard when compared to the other servers on your machine.