| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
properly initialized.
However, in practice the loader initializes them with zero, the
desired value, so there were no actual issue in almost all cases.
|
|
|
|
|
|
|
| |
currently being accessed buffer could be overwritten with new data.
While this probably did not cause access violations, it could case loss
and/or duplication of some data (definitely a race with no deterministic
outcome)
|
|
|
|
|
| |
predicate was not properly checked when waiting for the background file
writer
|
|
|
|
|
| |
Internal data structures were not properly protected due to missing
mutex calls.
|
|
|
|
| |
(this is primarily meant as a debug aid)
|
|
|
|
| |
This could only happen during config file parsing.
|
|
|
|
|
|
| |
Previously, it could lead to garbagge output and, in extreme cases, also
to segfaults. Note: this was a problem only when debug output was
actually enabled, so it caused no problem in production use.
|
|
|
|
|
|
|
|
|
|
| |
- improved testbench
- bugfix: potential data loss during file stream shutdown
- bugfix: potential problems during file stream shutdown
The shutdown/close sequence was not clean, what potentially (but
unlikely) could lead to some issues. We have not been able to describe
any fatal cases, but there was some bug potential. Sequence has now
been straighted out.
|
|
|
|
|
|
|
|
|
|
| |
When a write error occured in stream.c, variable iWritten had the error
code but this was handled as if it were the actual number of bytes
written. That was used in pointer arithmetic later on, and thus could
lead to all sorts of problems. However, this could only happen if the
error was EINTR or the file in question was a tty. All other cases were
handled properly. Now, iWritten is reset to zero in such cases, resulting
in proper retries.
|
| |
|
|
|
|
|
| |
primarily to ease migration from syslog-ng. See property replacer doc for
details. [backport from 5.5.3 because urgently needed by some]
|
| |
|
|
|
|
| |
including proper credits to Mandriva team.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- bugfix: potential segfault in omfile when a dynafile open failed
In that case, a partial cache entry was written, and some internal
pointers (iCurrElt) not correctly updated. In the next iteration, that
could lead to a segfault, especially if iCurrElt then points to the
then-partial record. Not very likely, but could happen in practice.
- bugfix (theoretical): potential segfault in omfile under low memory
condition. This is only a theoretical bug, because it would only
happen when strdup() fails to allocate memory - which is highly
unlikely and will probably lead to all other sorts of errors.
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
runtime/ctok.c
|
| |
| |
| |
| |
| | |
...and thus could not be used.
but tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=119
|
| |
| |
| |
| |
| | |
bugtracker: http://bugzilla.adiscon.com/show_bug.cgi?id=181
Thanks to Christiano for reporting.
|
| |
| |
| |
| | |
while the rest of the entry correctly said it was stable.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- improved testbench to contain samples for totally malformed messages
which miss parts of the message content
- bugfix: some malformed messages could lead to a missing LF inside files
or some other missing parts of the template content.
- bugfix: if a message ended immediately with a hostname, the hostname
was mistakenly interpreted as TAG, and localhost be used as hostname
|
| |
| |
| |
| |
| |
| |
| | |
[backported from v5 commit 98d1ed504ec001728955a5bcd7916f64cd85f39f]
This actually was a "recent" regression, but I did not realize that it
was introduced by the performance optimization in v4-devel. Shame on
me for having two devel versions at the same time...
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- bugfix: property replacer returned invalid parameters under some (unusual)
conditions. In extreme cases, this could lead to garbled logs and/or
a system failure.
- bugfix: invalid length returned (often) when using regular expressions
inside the property replacer
- bugfix: submatch regex in property replacer did not honor "return 0 on
no match" config case
|
| |
| |
| |
| | |
converted to html, linked, etc...
|
| |
| |
| |
| | |
Thanks to Ryan Lynch for reporting this.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
correct value on FreeBSD.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/queue.c
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/queue.c
|
| | |
| | |
| | |
| | |
| | | |
regression from introduction of "debug on demand" mode
Thanks to Michael Biebl for reporting this bug
|
| | |
| | |
| | |
| | |
| | |
| | | |
This could reslult in the whole rest of a line (including comments)
to be treated as file name in "write to file" actions.
Thanks to Jack for reporting this issue.
|
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for reporting this bug.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | | |
thanks to varmojfekoj for pointing me at this bug
|
| | |
| | |
| | |
| | | |
for example imudp. Thanks to Anton for reporting this bug.
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | | |
default thus was random (but most often "on")
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
|\| | |
|
| | | |
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=157
Thanks to Jonas Nogueira for reporting this bug.
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|