source: trunk/third/sysinfo/sysinfo.cf.man @ 12269

Revision 12269, 4.6 KB checked in by ghudson, 26 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r12268, which included commits to RCS files with non-trunk default branches.
Line 
1.\"
2.\" Copyright (c) 1992-1998 Michael A. Cooper.
3.\" This software may be freely distributed provided it is not sold for
4.\" profit and the author is credited appropriately.
5.\"
6.\" $Revision: 1.1.1.2 $
7.\"
8.TH sysinfo.cf 5 "22 April 1998"
9.ds ]W MagniComp
10.SH NAME
11sysinfo.cf \- Configuration File for sysinfo
12.SH SYNOPSIS
13\fBConfDir \fIPathName\fR
14.br
15.sp
16\fBDefine | \fIType | StringKey | NumericKey | Value1 | Value 2\fR
17.br
18.sp
19\fBDevice | \fIName | Type\fB/[\fISubType\fB]\fI | NumericID |
20Model | Description | Flags | DevFiles\fR
21.br
22.sp
23\fBInclude \fIFileName\fR
24.SH DESCRIPTION
25.B sysinfo.cf
26files are parsed by the
27.B sysinfo
28program.  Text starting with ``#'' and continuing
29to the end of the line is
30ignored.  Each line starts with a specific keyword as described below.
31All leading and trailing white space (space and TAB characters) for
32each field is removed before parsing.
33All keywords are case insensitive.
34The valid keywords are:
35.IP "\fBConfDir \fIPathName\fR"
36Set the name of the directory to look for configuration files in to
37be \fIPathName\fR.
38This also sets the value of the
39.B ${ConfDir}
40variable available for use with the
41.B Include
42keyword.
43The default is
44.B /var/local/sysinfo/conf
45.IP "\fBDefine \fIfields\fR"
46Definetion.  Each
47field is seperated by a ``|'' character.  Any fields that are not
48specified are initialized to NULL.
49The
50.I StringKey
51and/or
52.I NumericKey
53fields are used in matching search criteria.
54The specification for each field follows:
55.RS
56.IP \fIType\fR
57Specify the definetion type.  The following
58.I Type
59values are allowed:
60\fB
61CPU,
62Category,
63KArch,
64Kernel,
65NetType,
66OBP,
67Part,
68SysConf,
69SysModel,
70TapeInfo,
71VPD
72\fR
73.IP \fIStringKey\fR
74A string to use as a key.
75.IP \fINumericKey\fR
76A numeric value to use as a key.
77.IP \fIValue1\fR
78A string to return for the entry.
79.IP \fIValue2\fR
80A string to return for the entry.
81.RE
82.IP "\fBDevice \fIfields\fR"
83Device specification.  Each
84field is seperated by a ``|'' character.  Any fields that are not
85specified are initialized to NULL.
86The specification for each field follows:
87.RS
88.IP \fIName\fR
89The name of the device.
90( e.g.
91.B sd,
92.B cgsix
93)
94.IP "\fIType\fB/[\fISubType\fB]\fR"
95The type of device. 
96The
97.I Type
98value is used to determine how to
99.I probe
100the device and what device type label to assign to it.
101If
102.I SubType
103is specified, then the
104.I Type
105field specifies how to
106.I probe
107the device and the
108.I SubType
109field specifies what device type label to assign.
110The valid keywords are:
111.br
112\fB
113Bus,
114CDROM,
115CPU,
116Device,
117DiskCtlr,
118DiskDrive,
119FrameBuffer,
120Generic,
121KeyBoard,
122Memory,
123NetIF,
124Pseudo,
125TapeCtlr,
126TapeDrive
127\fR
128.IP \fINumericID\fR
129Specifies a unique numeric identifier for a particuliar device type.
130This field is typically used to find a device by a numeric value
131returned from the kernel.
132.IP \fIModel\fR
133The device's model.
134.IP \fIDescription\fR
135A description of the device.
136.IP \fIFlags\fR
137The
138.I Flags
139field may contain either a valid keyword or a numeric value.
140Numeric values are used in a device-type specific manner by the
141device type's probe routine.
142The valid keywords are:
143.RS
144.IP \fBDefInfo\fR
145Use default device definetion information.
146Usage varies by device type.
147.IP \fBLenCmp\fR
148Compare device name by length.
149.IP \fBNoUnit\fR
150Don't add a unit number to the device's name.
151.IP \fBZombie\fR
152If the device is present, treat it as if it were
153alive regardless of whether the kernel has
154indicated so.
155.RE
156.IP \fIDevFiles\fR
157A list of space seperated device files that provide access
158to the device.
159Each file may contain a
160.B `%d'
161which will be expanded to be the device's unit number.
162.RE
163.IP "\fBInclude \fIFileName\fR"
164Read and parse a
165.B sysinfo.cf
166file called
167.I FileName.
168Parsing of the current file resumes on the next line when finished
169with
170.I FileName.
171If
172.I FileName
173does not exist, sysinfo will silently continue parsing the current file.
174.I FileName
175may contain variables that are expanded at runtime.
176Variable names are enclosed inside of
177.B ${}
178or
179.B $()
180and are case insensitive.
181The following variables are available:
182.RS
183.IP \fB${ConfDir}\fR
184The path to the
185.B sysinfo
186configuration directory.
187.IP \fB${DefConfFile}\fR
188The name of the default
189.B sysinfo.cf
190configuration file.
191( e.g.
192.B Default.cf
193)
194.IP \fB${OSname}\fR
195The name of the operating system.
196( e.g.
197.B SunOS
198)
199.IP \fB${OSver}\fR
200The operating system version number.
201( e.g.
202.B 4.1.3
203)
204.IP \fB${OSmajver}\fR
205The operating system major version number.
206( e.g. for
207.B 4.1.3
208the value would be
209.B 4
210)
211.RE
212.SH AUTHOR
213Michael A. Cooper
214.br
215MagniComp Systems
216.br
217mcooper@magnicomp.com
218.SH "HOME PAGE"
219.B http://www.magnicomp.com/sysinfo/
220.SH SEE ALSO
221sysinfo(1)
222.SH DIAGNOSTICS
223.SH BUGS
Note: See TracBrowser for help on using the repository browser.