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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
Template: logtool/manual
Type: boolean
Default: true
_Description: Manual configuration of logtool's database?
Logtool needs a database with regular expressions that describe logfile
entries that should be ignored, or considered less important. You can
write this database manually, or use the very flexible database in the
package logcheck-database for this purpose.
.
If you choose to use logcheck-database and already added values to the
files in /etc/logtool, these files will be replaced by symbolic links in
the logcheck database (although backups will be preserved). Make sure this
is not unwanted behaviour.
.
Reply positively to manually write a database, or negatively to use the
database from the package "logcheck-database".
.
Note: since logtool does not depend on this database (but instead
Recommends it), the default answer to this question is to manually
configure the database.
Template: logtool/ignore-start
Type: select
Choices: paranoid, server, workstation
Default: paranoid
Description: Ignored template
No longer used template (although its value is read for upgrade purposes),
no need to translate it.
Template: logtool/use-level
Type: boolean
Default: true
# NOTE to translators: The terms 'paranoid', 'server', 'workstation',
# 'violations', 'cracking', and 'violations-ignore' refer to file names in
# /etc/logcheck. To avoid user confusion, these terms should either NOT be
# translated, or the translated terms should be mentioned between brackets
# after the untranslated version, like so:
# violations (inbreuken).
# Or, if you prefer, the other way around.
_Description: Do you want to use the '${level}' level regular expressions?
The database in the logcheck-database package defines three levels:
paranoid, server, and workstation; and it also has a database for cracking,
violations, and ignored violations ('violations-ignore'). Logcheck allows you
to pick one of the levels, and ignores the rest.
.
Logtool, on the other hand, can use multiple databases, which either
specify lines that should be completely excluded from output
(/etc/logtool/exclude) or lines that should be given a specific color
(green, yellow, blue, magenta, cyan, brightcyan). There is also the
possibility to not create an exclude file, and use an 'include' style of
file instead; its use is not recommended. Last but not least, files that
are not excluded from output but that do not match any other regular
expression are colored red.
.
If you want to map the '${level}' level database of regular expressions to
one of the above specified options, then answer positively to this
question.
Template: logtool/map-level-to-file
Type: select
_Choices: exclude, include, green, yellow, blue, magenta, cyan, brightcyan
_Description: What do you want the ${level} level of regular expressions to do?
Please specify what you want to do with a line if it matches at least one
of the regular expressions in the ${level} level database. You have the
following options (note that regular expressions are matched on a
line-per-line basis):
.
* exclude: discard matching lines
* include: discard all but matching lines. Not recommended. Note that
this is mutually exclusive with 'exclude'.
* green, yellow, blue, magenta, cyan, brightcyan: give matching lines
the specified color.
.
Note that each option can be specified for only one of paranoid,
server, or workstation.
Template: logtool/error-multiple
Type: error
_Description: Please do not select an action more than once
You have selected the action ${action} for at least ${level1} and
${level2}. This is invalid; please either select a unique action for each
level, or go back and choose not to use a certain level.
|
