| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
The bug fixes actually fixes a bug inside the *testbench* itself.
|
| |
|
| |
|
|
|
|
|
|
| |
files
Unfortunately, this is often the case by default in many distros.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most importantly, the last patch for imfile contained a number
of glitches, which are fixed by this commit (a memory leak under
unusual conditions, partial message loss when rsyslog was
terminated in the interim & mixing file data to the wrong files
when multiple monitors were used [due to static variable]). The
commit is actually a re-write of the patch, based on its core
idea.
Also some other minor cleanup was done.
|
| |
|
|
|
|
|
|
|
|
|
| |
File lines that were incomplete (LF missing) *at the time imfile polled
the file* were partially discarded. That part of the line that was read
without the LF was discarded, and the rest of the line was submitted in
the next polling cycle. This is now changed so that the partial content
is saved until the complete line is read. Note that the patch affects
only read mode 0.
|
|
|
|
|
|
|
| |
If the property name was followed by a space before the comma, rsyslogd
aborted on startup. Note that no segfault could happen if the initial
startup went well (this was a problem with the config parser).
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=381
|
|
|
|
|
|
|
| |
The length for the field name was invalidly computed, resulting in either
truncated field names or including extra random data. If the random data
contained NULs, the rest of the message became unreadable.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=374
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This is not a real problem (thus no ChangeLog entry): we leaked a few
bytes for every relp listener, but only at rsyslogd TERMINATION - where
obviously the OS does the cleanup. However, the leak could cause some
confusion with memory checkers like valgrind.
|
|
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=380
|
|
|
|
|
| |
The indentation around the "-d" flag description is in the
wrong place and does not display properly.
|
|
|
|
|
|
|
| |
The processing loop was not terminated when an unaccessible file was
detected, and so processing was done using unitialized data, which
could lead to all sorts of problems.
Also did some minor cleanup.
|
|
|
|
| |
This will avoid an error message when including an empty directory.
|
|\ |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| | | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=376
The testbench was also enhanced to check for these cases.
Thanks to Georgi Georgiev for the bug report.
Also minor bugfix: no error msg on unreadable $IncludeConfig path
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This could happen in RainerScript comparisons (like contains); in some
cases an unitialized variable was accessed, which could lead to an
invalid free and in turn to a segfault.
Closes: http://bugzilla.adiscon.com/show_bug.cgi?id=372
Thanks to Georgi Georgiev for reporting this bug and his great help
in solving it.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this enables smoother builds on older systems that do not support
libuuid. Loss of functionality should usually not matter too much as
uuid support has only recently been added and is very seldom used.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The doc contained a previous default, which has been changed in
the mean time.
|
| | | | |
|
|\ \ \ \
| | |/ /
| |/| | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Both are closely related and thus rolled into a single commit.
- bugfix: improper handling of backslash in string-type template()s
- bugfix: leading quote (") in string-type template() lead to thight loop
on startup
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Thanks to oxpa for the patch.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=371
|
|\| | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On many platforms, this has no effect at all. At some, it may cause
a segfault. The problem occurs only during config phase, no segfault
happens when rsyslog has fully started.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We also added a testbench test to check for this in the future. That
in turn required new testbench tools.
|
| |/ /
|/| |
| | |
| | | |
... due to too small timeout for enqueue processing --> messages got lost
|
| | | |
|