Additional setup
57
notice
– Events related to the application business logics.
info
– General information concerning the application functionality.
debug
– Debugging messages.
all
– All the above levels.
You can combine the information categories and their detail levels. For example,
if you want to record all information related to backing up messages, enter the
following string into the configuration file:
LogOption=backup.all
To log only configuration errors, type the following:
LogOption=config.error
To prevent some information from logging, type, for example, the following:
LogOption=-scan.debug
The minus before the combination means that this category will be excluded from
logging. The remaining information will be logged.
When the
LogFacility
is
file
, all log messages are written in the same file. This
file can grow rather large, making recording slower.
To avoid delayed writing, you should enable the rotation of log file
(
LogRotate=on
). In this mode, when the report file grows and reaches
RotateSize
,
it is
copied to
kavmilter.<number>.log
and the initial log truncates to
zero. The
RotateRounds
keyword specifies how many different rotation rounds
can occur. The
<number>
in rotated log file name specifies what round that is.
Since one of the purposes of log rotation is to avoid logs taking up space, when
the
RotateRounds
number or rotations is reached), it starts writing over the old
ones.
For example, when
RotateSize=1048576
and
RotateRounds=10
then
kavmilter.1.log
,
kavmilter.2.log etc
. will be created, each
1048576
bytes. After
kavmilter.10.log
is created and it has reached 1048576 bytes,
kavmilter.1.log
is
overwritten on the next rotation, and so on.
6.13. Parameters of update report
generation
Updating results are logged in a report that can be saved to the system log or as
a separate file (
ReportFileName
parameter of the
[updater.report]
section).
You can adjust the amount of output information by changing the
report detail
level
.
