source: trunk/athena/etc/larvnetd/larvnet.conf.5 @ 12051

Revision 12051, 4.5 KB checked in by ghudson, 26 years ago (diff)
Support grouping of net names into a single report name. To properly handle reloading of the config file, this means remembering the reported net name and translating it to a report name at report time.
Line 
1.\" $Id: larvnet.conf.5,v 1.2 1998-10-13 17:12:58 ghudson Exp $
2.\"
3.\" Copyright 1998 by the Massachusetts Institute of Technology.
4.\"
5.\" Permission to use, copy, modify, and distribute this
6.\" software and its documentation for any purpose and without
7.\" fee is hereby granted, provided that the above copyright
8.\" notice appear in all copies and that both that copyright
9.\" notice and this permission notice appear in supporting
10.\" documentation, and that the name of M.I.T. not be used in
11.\" advertising or publicity pertaining to distribution of the
12.\" software without specific, written prior permission.
13.\" M.I.T. makes no representations about the suitability of
14.\" this software for any purpose.  It is provided "as is"
15.\" without express or implied warranty.
16.\"
17.TH LARVNET.CONF 5 "23 Aug 1998"
18.SH NAME
19/etc/athena/larvnet.conf \- larvnetd configuration file
20.SH DESCRIPTION
21The file
22.B /etc/athena/larvnet.conf
23configures what cluster machines and printers are to be monitored by
24the
25.BR larvnetd (8)
26daemon.
27.PP
28The file is divided into two sections, separated by a line beginning
29with '-'.  The first section gives the architecture names, one per
30line; empty lines or lines beginning with '#' are ignored.  Each line
31consists of a name to be used as a column heading and, optionally, one
32or more corresponding architecture names which may be reported by
33workstations for that column heading.  If only a column heading is
34given, the column heading is also used as the sole architecture name.
35The order of the architecture names gives the order of the output
36columns in the cluster report file (see
37.BR larvnet.clusters (5)),
38and thus the order of columns in the output of
39.BR cviewd (8).
40.PP
41The second section gives the actual cluster machines as well as
42printers.  Leading and trailing whitespace are ignored, as well as any
43text after the first '#' character; empty lines or lines containing
44only whitespace and comments are ignored entirely.  Lines in this
45section may have one of the following formats:
46.TP 8
47\fBcluster\fP \fIname\fP \fIphone\fP
48Introduces a new cluster.  The first field should not exceed seven
49letters in the current cview output format.  The second argument
50should give the cluster phone number or "(none)".
51.TP 8
52\fBws\fP \fIname\fP
53Lists a machine name within a cluster.  This line must appear after a
54.B cluster
55line.  The workstation name may include a numeric range in square
56brackets.  For example, "w20-575-[1-50]" would expand to fifty
57workstations.
58.TP 8
59\fBprinter\fP \fIname\fP
60Lists a printer within a cluster.  This line must appear after a
61.B cluster
62line.  The printer name's
63.B pcap
64entry will be looked up in Hesiod to find the print server name, which
65will in turn be looked up in the DNS.  If either lookup fails, the
66printer entry will be ignored.
67.TP 8
68\fBcgroup\fP \fIname\fP \fIx\fP \fIy\fP \fIcluster\fP ...
69Specifies a group of public clusters.  The
70.I x
71and
72.I y
73numbers give the position of the cluster group on the cluster map
74(see
75.BR xcluster (1)).
76The
77.I cluster
78parameters must be clusters which have already been specified in the
79configuration file and which have not already been assigned to a
80cluster group.
81.TP 8
82\fBoption report-other\fP \fIcolname\fP In the report file, generate
83statistics for workstations reporting an architecture which does not
84match any line in the first section of the file.  Use the parameter
85.I colname
86as the architecture name.
87.TP 8
88\fBoption report-unknown\fP \fIcolname\fP
89In the report file, generate statistics for workstations which have
90not yet sent a status packet to the server and are thus of unknown
91architecture.  Use the parameter
92.I colname
93as the architecture name.
94.SH EXAMPLE
95The following example tells larvnetd to monitor 126 machines and five
96printers in two clusters, one of which is in a cluster group named
97"W20" and located at X coordinate 30828 and Y coordinate 18254.
98.PP
99.RS
100.nf
101SPARC/4
102SPARC/5
103Ultra-5_10 SUN/ULTRA
104IP32 SGI/O2
105IP22 SGI/INDY
106---
107option report-other OTHER
108cluster SIPB 3-7788
109        ws x15-cruise-basselope.mit.edu
110        ws steve-dallas.mit.edu
111        ws opus.mit.edu
112        ws reaper-man.mit.edu
113        # Don't list printer meadow since there is no support for
114        # private printers currently.
115cluster W20-575 3-0103
116        ws w20-575-[1-120].mit.edu
117        ws test-sgi.mit.edu
118        ws test-sparc4.mit.edu
119        printer ajax
120        printer ceres
121        printer python
122        printer fiber
123        printer pulp
124cgroup W20 30828 18254 W20-575
125.fi
126.RE
127.SH SEE ALSO
128.BR larvnetd (8)
129.SH AUTHOR
130Greg Hudson, MIT Information Systems
131.br
132Copyright 1998 by the Massachusetts Institute of Technology.
Note: See TracBrowser for help on using the repository browser.