summaryrefslogtreecommitdiff
path: root/security/logcheck/files/patch-docs_logcheck-test.1
blob: d5a229cf96d4104cc0dc3ace4a387873295a5e2c (plain) (blame)
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
--- docs/logcheck-test.1.orig	2017-01-25 21:08:04 UTC
+++ docs/logcheck-test.1
@@ -4,7 +4,7 @@ logcheck-test \- test new logcheck rules
 .SH SYNOPSIS
 .B logcheck\-test
 .RB [ \-q | \-i ]
-.RB [ \-a | \-s | \-l
+.RB [ \-a | \-m | \-l
 .IR FILE ]
 .RB [ \-e ]
 .RB [ \-P
@@ -15,7 +15,7 @@ logcheck-test \- test new logcheck rules
 .br
 .B logcheck\-test
 .RB [ \-q | \-i ]
-.RB [ \-a | \-s | \-l
+.RB [ \-a | \-m | \-l
 .IR FILE ]
 .B \-r
 .I RULEFILE
@@ -38,8 +38,8 @@ Show usage information
 .B \-a, \-\-auth.log
 Parse /var/log/auth.log for matching lines
 .TP
-.B \-s, \-\-syslog
-Parse /var/log/syslog for matching lines
+.B \-m, \-\-messages
+Parse /var/log/messages for matching lines
 .TP
 .B \-l, \-\-log\-file FILE
 Parse FILE for matching lines
@@ -69,10 +69,10 @@ With
 .B logcheck-test
 you can easily write and test new rules.
 .PP
-Test a single rule against /var/log/syslog:
+Test a single rule against /var/log/messages:
 .RS
 .fam C
-logcheck-test \-s "RULE"
+logcheck-test \-m "RULE"
 .fam T
 .RE