| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This also made necessary some parser test case updates. Acutally, the test
case was wrong, but I did not notice that before.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
doc/manual.html
tools/syslogd.c
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- 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...
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
tests/parsertest.sh
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
template.c
tests/Makefile.am
tests/parsertest.sh
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
now CSV and regex extraction are being tested (would have caught the
bug fixed with the last commit).
|
| | | |
|
| | |
| | |
| | |
| | | |
Thanks to David Lang for suggesting this functionality.
|
| | |
| | |
| | |
| | |
| | | |
existed for some time, had forgotten to add it to git. Not an
important case, though...
|
| | | |
|
|/ /
| |
| |
| |
| | |
Based on Jonathan Bond-Caron's patch for v4. This now also includes some
automatted tests.
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
doc/rsyslog_conf_modules.html
tests/Makefile.am
tests/sndrcv_drvr.sh
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
...by replacing time() call with much faster (at least under linux)
gettimeofday() calls.
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| |\| |
|
| | |\
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was a regression from the time() optimizations done in v4.
Bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=143
Thanks to Klaus Tachtler for reporting this bug.
|
| | | | |
|
|\| | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
also prepared test case for TLS testing, but not activated it
inside the build itself.
A note on TLS testing: the current testsuite (in git!) already contains
TLS test cases. However, getting these test cases correct is not simple.
That's not a problem with the code itself, but rater a problem with
synchronization in the test environment. So I have deciced to keep the
TLS tests in, but not yet actually utilize them. This is most probably
left as an excercise for future (devel) releases.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... also improved two-instance test mechanism, now have a generic
approach.
|
| | | |
| | | |
| | | |
| | | | |
... plus a simple initial test of the tcp forwarding capability.
|
| | | |
| | | |
| | | |
| | | | |
... also bumped version number
|
|\| | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
thus some unpredictable behavior and a false negative test result
could occur. [BACKPORTED from v5]
|
| | |\|
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
runtime/msg.c
|
| | | |
| | | |
| | | |
| | | | |
... getting the module structure a bit cleaner ;)
|
|\| | | |
|
| | | | |
|
| |\ \ \
| | |/ /
| |/| /
| | |/
| | |
| | | |
Conflicts:
ChangeLog
runtime/msg.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
This resulted in build errors if no Java was present on the build system,
even though none of the selected option actually required Java.
(I forgot to backport a similar fix to newer releases).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
processing.
THIS IS A VERY IMPORTANT ADDITION, see its doc for why.
|
| | |
| | |
| | |
| | |
| | | |
thus some unpredictable behavior and a false negative test result
could occur.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
actually, the runtime dummy was missing some global entities, these
have now been added.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problems could happen if the queue worker needed to be cancelled
and this cancellation happened inside queue-code (including
wtp, wti). We have now solved this by disabling cancellation while
in this code and only enabling it when working inside the user consumer.
This exactly matches the use case for which cancellation may be needed.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
these occured in very unusual scenarios where we had a DA-queue running
in parallel and very lengthy actions. Then, in some situations, the
shutdown could hang. The code needs some addition lab time, but
is believed to be much better than any previous version.
|
| | |
| | |
| | |
| | |
| | | |
We do now enqueue those objects that are left unprocessed. This enables
us to delete the full batch, what is exactly what we need to do.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... but this brings a lot of problems with it. The issue is that
we still have a sequential store and we do not know how we could
delete the one entry right in the middle of processing. I keep this
branch if we intend to move on with it - but for now I look into a
different solution...
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
support for enhancing probability of memory addressing failure by
using non-NULL default value for malloced memory (optional, only if
requested by configure option). This helps to track down some
otherwise undetected issues within the testbench and is expected
to be very useful in the future.
|