source: branches/samba-3.3.x/docs/manpages/eventlogadm.8@ 368

Last change on this file since 368 was 368, checked in by Herwig Bauernfeind, 16 years ago

Update Samba 3.3 to 3.3.10 (docs)

File size: 5.9 KB
Line 
1'\" t
2.\" Title: eventlogadm
3.\" Author: [see the "AUTHOR" section]
4.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
5.\" Date: 01/14/2010
6.\" Manual: System Administration tools
7.\" Source: Samba 3.3
8.\" Language: English
9.\"
10.TH "EVENTLOGADM" "8" "01/14/2010" "Samba 3\&.3" "System Administration tools"
11.\" -----------------------------------------------------------------
12.\" * set default formatting
13.\" -----------------------------------------------------------------
14.\" disable hyphenation
15.nh
16.\" disable justification (adjust text to left margin only)
17.ad l
18.\" -----------------------------------------------------------------
19.\" * MAIN CONTENT STARTS HERE *
20.\" -----------------------------------------------------------------
21.SH "NAME"
22eventlogadm \- push records into the Samba event log store
23.SH "SYNOPSIS"
24.HP \w'\ 'u
25eventlogadm [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ addsource\ \fIEVENTLOG\fR\ \fISOURCENAME\fR\ \fIMSGFILE\fR
26.HP \w'\ 'u
27eventlogadm [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ write\ \fIEVENTLOG\fR
28.SH "DESCRIPTION"
29.PP
30This tool is part of the
31\fBsamba\fR(1)
32suite\&.
33.PP
34eventlogadm
35is a filter that accepts formatted event log records on standard input and writes them to the Samba event log store\&. Windows client can then manipulate these record using the usual administration tools\&.
36.SH "OPTIONS"
37.PP
38\fB\-d\fR
39.RS 4
40The
41\-d
42option causes
43eventlogadm
44to emit debugging information\&.
45.RE
46.PP
47\fB\-o\fR addsource \fIEVENTLOG\fR \fISOURCENAME\fR \fIMSGFILE\fR
48.RS 4
49The
50\-o addsource
51option creates a new event log source\&.
52.RE
53.PP
54\fB\-o\fR write \fIEVENTLOG\fR
55.RS 4
56The
57\-o write
58reads event log records from standard input and writes them to the Samba event log store named by EVENTLOG\&.
59.RE
60.PP
61\fB\-h\fR
62.RS 4
63Print usage information\&.
64.RE
65.SH "EVENTLOG RECORD FORMAT"
66.PP
67For the write operation,
68eventlogadm
69expects to be able to read structured records from standard input\&. These records are a sequence of lines, with the record key and data separated by a colon character\&. Records are separated by at least one or more blank line\&.
70.PP
71The event log record field are:
72.sp
73.RS 4
74.ie n \{\
75\h'-04'\(bu\h'+03'\c
76.\}
77.el \{\
78.sp -1
79.IP \(bu 2.3
80.\}
81
82LEN
83\- This field should be 0, since
84eventlogadm
85will calculate this value\&.
86.RE
87.sp
88.RS 4
89.ie n \{\
90\h'-04'\(bu\h'+03'\c
91.\}
92.el \{\
93.sp -1
94.IP \(bu 2.3
95.\}
96
97RS1
98\- This must be the value 1699505740\&.
99.RE
100.sp
101.RS 4
102.ie n \{\
103\h'-04'\(bu\h'+03'\c
104.\}
105.el \{\
106.sp -1
107.IP \(bu 2.3
108.\}
109
110RCN
111\- This field should be 0\&.
112.RE
113.sp
114.RS 4
115.ie n \{\
116\h'-04'\(bu\h'+03'\c
117.\}
118.el \{\
119.sp -1
120.IP \(bu 2.3
121.\}
122
123TMG
124\- The time the eventlog record was generated; format is the number of seconds since 00:00:00 January 1, 1970, UTC\&.
125.RE
126.sp
127.RS 4
128.ie n \{\
129\h'-04'\(bu\h'+03'\c
130.\}
131.el \{\
132.sp -1
133.IP \(bu 2.3
134.\}
135
136TMW
137\- The time the eventlog record was written; format is the number of seconds since 00:00:00 January 1, 1970, UTC\&.
138.RE
139.sp
140.RS 4
141.ie n \{\
142\h'-04'\(bu\h'+03'\c
143.\}
144.el \{\
145.sp -1
146.IP \(bu 2.3
147.\}
148
149EID
150\- The eventlog ID\&.
151.RE
152.sp
153.RS 4
154.ie n \{\
155\h'-04'\(bu\h'+03'\c
156.\}
157.el \{\
158.sp -1
159.IP \(bu 2.3
160.\}
161
162ETP
163\- The event type \-\- one of "INFO", "ERROR", "WARNING", "AUDIT SUCCESS" or "AUDIT FAILURE"\&.
164.RE
165.sp
166.RS 4
167.ie n \{\
168\h'-04'\(bu\h'+03'\c
169.\}
170.el \{\
171.sp -1
172.IP \(bu 2.3
173.\}
174
175ECT
176\- The event category; this depends on the message file\&. It is primarily used as a means of filtering in the eventlog viewer\&.
177.RE
178.sp
179.RS 4
180.ie n \{\
181\h'-04'\(bu\h'+03'\c
182.\}
183.el \{\
184.sp -1
185.IP \(bu 2.3
186.\}
187
188RS2
189\- This field should be 0\&.
190.RE
191.sp
192.RS 4
193.ie n \{\
194\h'-04'\(bu\h'+03'\c
195.\}
196.el \{\
197.sp -1
198.IP \(bu 2.3
199.\}
200
201CRN
202\- This field should be 0\&.
203.RE
204.sp
205.RS 4
206.ie n \{\
207\h'-04'\(bu\h'+03'\c
208.\}
209.el \{\
210.sp -1
211.IP \(bu 2.3
212.\}
213
214USL
215\- This field should be 0\&.
216.RE
217.sp
218.RS 4
219.ie n \{\
220\h'-04'\(bu\h'+03'\c
221.\}
222.el \{\
223.sp -1
224.IP \(bu 2.3
225.\}
226
227SRC
228\- This field contains the source name associated with the event log\&. If a message file is used with an event log, there will be a registry entry for associating this source name with a message file DLL\&.
229.RE
230.sp
231.RS 4
232.ie n \{\
233\h'-04'\(bu\h'+03'\c
234.\}
235.el \{\
236.sp -1
237.IP \(bu 2.3
238.\}
239
240SRN
241\- The name of the machine on which the eventlog was generated\&. This is typically the host name\&.
242.RE
243.sp
244.RS 4
245.ie n \{\
246\h'-04'\(bu\h'+03'\c
247.\}
248.el \{\
249.sp -1
250.IP \(bu 2.3
251.\}
252
253STR
254\- The text associated with the eventlog\&. There may be more than one string in a record\&.
255.RE
256.sp
257.RS 4
258.ie n \{\
259\h'-04'\(bu\h'+03'\c
260.\}
261.el \{\
262.sp -1
263.IP \(bu 2.3
264.\}
265
266DAT
267\- This field should be left unset\&.
268.SH "EXAMPLES"
269.PP
270An example of the record format accepted by
271eventlogadm:
272.sp
273.if n \{\
274.RS 4
275.\}
276.nf
277 LEN: 0
278 RS1: 1699505740
279 RCN: 0
280 TMG: 1128631322
281 TMW: 1128631322
282 EID: 1000
283 ETP: INFO
284 ECT: 0
285 RS2: 0
286 CRN: 0
287 USL: 0
288 SRC: cron
289 SRN: dmlinux
290 STR: (root) CMD ( rm \-f /var/spool/cron/lastrun/cron\&.hourly)
291 DAT:
292
293.fi
294.if n \{\
295.RE
296.\}
297.PP
298Set up an eventlog source, specifying a message file DLL:
299.sp
300.if n \{\
301.RS 4
302.\}
303.nf
304 eventlogadm \-o addsource Application MyApplication | \e\e
305 %SystemRoot%/system32/MyApplication\&.dll
306
307.fi
308.if n \{\
309.RE
310.\}
311.PP
312Filter messages from the system log into an event log:
313.sp
314.if n \{\
315.RS 4
316.\}
317.nf
318 tail \-f /var/log/messages | \e\e
319 my_program_to_parse_into_eventlog_records | \e\e
320 eventlogadm SystemLogEvents
321
322.fi
323.if n \{\
324.RE
325.\}
326.SH "VERSION"
327.PP
328This man page is correct for version 3\&.0\&.25 of the Samba suite\&.
329.SH "AUTHOR"
330.PP
331The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
Note: See TracBrowser for help on using the repository browser.