File: install-servers.pod

package info (click to toggle)
remstats 1.00a4-8woody1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 4,576 kB
  • ctags: 1,020
  • sloc: perl: 11,706; ansic: 2,776; makefile: 944; sh: 869
file content (84 lines) | stat: -rw-r--r-- 2,917 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
=cut

TITLE=Server Installation
DESCRIPTION=how to install remstats servers
KEYWORDS=servers
DOCTOP=index
DOCPREV=private
DOCNEXT=install-webserver

=pod


=head1 Server Installation

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

=over 4

=item Add entries for the servers in C</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 L<run-remstats>
to add the appropriate switches.

=item [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 @@GROUP@@
	useradd -g @@GROUP@@ -d @@INSTALLDIR@@ @@OWNER@@

=item Modify C</etc/inetd.conf> to get the servers invoked,
like this:

	unix-status	stream tcp nowait @@OWNER@@ @@INSTALLDIR@@/unix-status-server unix-status-server
	log-server	stream tcp nowait @@OWNER@@ @@INSTALLDIR@@/log-server log-server logfile1 logfile2
	
Or if you're using 
L<tcp_wrappers|ftp://ftp.porcupine.org/pub/security/tcp_wrappers_7.6.BLURB>, 
which you should be:

	unix-status	stream tcp nowait @@OWNER@@ /path/to/tcpd @@INSTALLDIR@@/unix-status-server
	log-server	stream tcp nowait @@OWNER@@ /path/to/tcpd @@INSTALLDIR@@/log-server logfile1 logfile2

And remember to update C</etc/hosts.allow> to allow your remstats host access.
	
=item Tell inetd to re-read it's config-file:

	kill -HUP pid-of-inetd

=for html <P></P>

=item copy the remstats servers to the machines which will run them

	rcp unix-status-server log-server remoteping-server multiping host:@@INSTALLDIR@@

=back 4

=head1 The nt-status-server

This one is a bit different to install.  I've only done it under the
L<ActiveState Perl|http://www.activestate.com/Products/ActivePerl/index.html> 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<C:\Perl\bin\perl.exe>), and the argument string something like:

	c:\wherever\you\put\nt-status-server -s -t10.111.12.13

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