blob: d71c0c4fe2c9f6e61199140a2b2e4e932e103f2e (
plain)
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
|
This file contains know bugs and incompatibilities
REPEATED LOG LINES
If multiple log lines with the exact same content are received,
the duplicates are NOT suppressed. This is done by sysklogd
in all cases. We plan to add this as an optional feature,
but as of now every line is logged.
ERRORS ON STARTUP
Error reporting on startup is not particular good. We handle all
errors correctly, but sometimes a message is only reported if
running in debug mode. If you experience some strange behaviour
I suggest to run the syslogd interactively with debugging enabled.
VERY LARGE LOG FILES
We have done nothing to support log files larger than 2GB. As such, it
behaves just like sysklogd in this regard. And, as far as I recall, this
means that - at least with certain glibc versions - no more than 2GB
will be written. This will be checked and supported at a later time, for
now just be careful ;).
EQUALLY-NAMED TEMPLATES
If multiple templates with the SAME name are created, all but the
first definition is IGNORED. So you can NOT (yet) replace a
template definition.
MEMORY LEAK ON HUPING
Currently, the template memory is NOT freed when SIGHUP is received.
This causes a small memory leak on each HUP. Will be fixed soon and
should not cause real trouble unless you HUP syslogd quite frequently.
Updates to the bug lists (and potential fixes...) can be found at the
official home page at
http://www.monitorware.com/rsyslog
List as of 2004-12-08
Rainer Gerhards
|