File: README

package info (click to toggle)
picalib 0.1.5-3
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 680 kB
  • ctags: 57
  • sloc: perl: 1,120; sh: 435; makefile: 76
file content (34 lines) | stat: -rw-r--r-- 1,096 bytes parent folder | download | duplicates (3)
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
PICA Library
============

$Id: README,v 1.4 2002/03/20 10:04:42 cvs Exp $

Miguel Armas <kuko@ulpgc.es>

This directory includes a lot of contributed files/alarms to help System
Administrators using PICA

Most of these alarms need the MLDBM Perl package

Admin Domain (admindomain)
==========================

Most of the alarms included use the concept of "admindomains". An admindomain
is a group of administratively related hosts. The idea is that within PICA
only hosts in the same admindomain will interact with each other.

For example, the NTP module generates a configuration where hosts belonging
to the ntpservers synchronize with each other, But you don't want servers
from client (or network) A synchronizing with servers from client B. The
answer is to define different admindomains for each client and include the
clients' hosts in that group.

This is done in a very simple way. Including all the hosts in a group
and defining the variable "admindomain" for that group:

hostgroup clientA {
    members { host1, host2, host3 }
    vars {
         admindomain = 'clientA';
    }
}