Remstats Home

  About remstats
  Release Notes
      the remstats user
      the webgroup group
      private functions
      remstats servers
      your web-server
  Configuration Tools

Live Data

Remstats was written by Thomas Erskine at the CRC in Canada and now looking for work.

[Top] [Prev] [Next]

Server Installation

One of the interesting things about remstats (I think), is the remote servers. To install them, you'll need to do a few things on each host which will run the servers:

  • Add entries for the servers in /etc/services, like this:
    	unix-status	1957/tcp	# remstats unix-status server
    	log-server	1958/tcp	# remstats log server

    You can run them on different ports, but these are the defaults and you'd have to change run-remstats to add the appropriate switches.

  • [Optional] Unless you're going to run the servers as root (unnecessary), you'll need to create the user that the servers will run as. The only reasons I can think of for running the servers as root are if you need to run them on a low-numbered port (<=1024), or if you need to read a log-file which isn't readable by the remstats user, or if you want to run multiping non-suid. On Linux and Solaris, you can do:
    	groupadd users
    	useradd -g users -d /home/groups/r/re/remstats terskine
  • Modify /etc/inetd.conf to get the servers invoked, like this:
    	unix-status	stream tcp nowait terskine /home/groups/r/re/remstats/unix-status-server unix-status-server
    	log-server	stream tcp nowait terskine /home/groups/r/re/remstats/log-server log-server logfile1 logfile2

    Or if you're using tcp_wrappers, which you should be:

    	unix-status	stream tcp nowait terskine /path/to/tcpd /home/groups/r/re/remstats/unix-status-server
    	log-server	stream tcp nowait terskine /path/to/tcpd /home/groups/r/re/remstats/log-server logfile1 logfile2

    And remember to update /etc/hosts.allow to allow your remstats host access.

  • Tell inetd to re-read it's config-file:
    	kill -HUP pid-of-inetd

  • copy the remstats servers to the machines which will run them
    	scp unix-status-server log-server remoteping-server multiping host:/home/groups/r/re/remstats

The nt-status-server

This one is a bit different to install. I've only done it under the ActiveState Perl under Windows NT 4.0. Installing the ActiveState Perl is straightforward; if you got here, you'll have no trouble with that. Installing it as a service is not as simple as I intended. You'll have to get the SRVANY and INSTSRV programs from the NT Resource Kit, and follow their instructions. The program that SRVANY will be running is, of course, perl (usually C:\Perl\bin\perl.exe), and the argument string something like:

	c:\wherever\you\put\nt-status-server -s -t

You'll have to replace c:\wherever\you\put with the path to nt-status-server, and with the IP number of the host running the nt-status-collector.

Or you can run it not as a service like:

	c:\wherever\you\put\nt-status-server -s -t -s -T

but you'll have to start and stop it by hand at the console.

It also needs the Win32::Daemon module, as noted on the required page. The simplest way to install this (under ActiveState), is to use the PPM program that came with ActiveState Perl. Like this:

	c:\> ppm
	ppm> set repository roth
	ppm> install Win32::Daemon
	ppm> exit

Currently, the code needs this module, even if it's invoked with the -s flag, which doesn't use the Win32::Daemon code at all.

[Top] [Remstats] [SourceWorks] [RRDtool] [SourceForge]
Last updated Fri May 30 13:50:55 PDT 2003 by <>.