| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|
|
|
| |
same issue as previous commit for PROGNAME and APPNAME
|
|
|
|
| |
could lead to invalid characters e.g. in dynamic file names
|
|
|
|
|
| |
previously, RS_RET_RESUME was returned, which lead to a loop inside the
rule engine as omfile could not really recover.
|
|
|
|
| |
Changed version to 5.8.5-pre1
|
|
|
|
|
| |
- bugfix: potential hang condition during tag emulation
- bugfix: too-early string termination during tag emulation
|
|
|
|
|
| |
The syslogtag of the duplicated message could get contain garbage at the end
as the string terminating NULL Byte was missing.
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Note that this actually is a very small change, but I needed
to shuffle a lot of code around in order to make it compile
(due to required define order...).
|
| |
|
|
|
|
|
|
|
|
|
| |
as well as potentially in a number of other places where MsgDup() was
used. This only happened when the imudp input module was used and it
depended on name resolution not yet had taken place. In other words,
this was a strange problem that could lead to hard to diagnose
instability. So if you experience instability, chances are good that
this fix will help.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/parser.c
runtime/queue.c
runtime/wtp.c
template.c
threads.c
tools/syslogd.c
|
| | |
|
| |
| |
| |
| |
| | |
At least one instance of that problem could potentially lead
to abort (inside omfile).
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.ac
runtime/cfsysline.c
tools/ompipe.c
|
| | |
|
| |
| |
| |
| |
| |
| | |
...message-induced off-by-one error (potential segfault) (see 4.6.2)
The analysis has been completed and a better fix been crafted and
integrated.
|
| |
| |
| |
| | |
also: bugfix: mutexes used to similate atomic instructions were not destructed
|
| |
| |
| |
| |
| |
| | |
and also provided four build-in modules for the most common use
cases, hopefully resulting in a speedup of around 5% for typical
rsyslog processing.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was a test done to try to generate templates with C code, via
a new (potentially to-be-implemented) class of template modules. We have
a rough POC inside this code, and it showed around 5% or better speedup. So
it semms worth continuing in this direction.
Note that this experimental commit works correct, but does any
template in the form of
$template tpl,=somewhat
will lead to fixed template expansion based on the default file format.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/Makefile.am
runtime/atomic.h
runtime/queue.c
runtime/queue.h
runtime/wti.c
runtime/wti.h
runtime/wtp.c
runtime/wtp.h
|
| | |
| | |
| | |
| | |
| | |
| | | |
replaced atomic operation emulation with new code. The previous code
seemed to have some issue and also limited concurrency severely. The
whole atomic operation emulation has been rewritten.
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
runtime/wtp.c
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
plugins/imudp/imudp.c
runtime/stream.h
tests/Makefile.am
tests/diag.sh
tools/omfile.c
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/Makefile.am
runtime/rsyslog.c
tests/nettester.c
tools/syslogd.c
|
| | |/
| | |
| | |
| | |
| | |
| | | |
this enables us to work with the "usual" environment tweaks (for
debugging and other purposes), without the need for any special
handling in nettester itself
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/debug.c
runtime/stream.c
tests/Makefile.am
tests/diskqueue.sh
tests/nettester.c
tools/omfile.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some types of malformed messages could trigger an off-by-one error
(for example, \0 or \n as the last character, and generally control
character escaption is questionable). This is due to not strictly
following a the \0 or string counted string paradigm (during the last
optimization on the cstring class). As a temporary fix, we have
introduced a proper recalculation of the size. However, a final
patch is expected in the future. See bug tracker for further details
and when the final patch will be available:
http://bugzilla.adiscon.com/show_bug.cgi?id=184
Note that the current patch is considered sufficient to solve the
situation, but it requires a bit more runtime than desirable.
|
| |\|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
runtime/datetime.h
|
| | |
| | |
| | |
| | |
| | | |
primarily to ease migration from syslog-ng. See property replacer doc for
details. [backport from 5.5.3 because urgently needed by some]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
[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...
|
| | |
| | |
| | |
| | |
| | | |
primarily to ease migration from syslog-ng. See property replacer doc
for details.
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
tests/parsertest.sh
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
template.c
tests/Makefile.am
tests/parsertest.sh
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- 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
|
| | |
| | |
| | |
| | | |
issues
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| |\| |
|
| | |
| | |
| | |
| | | |
for example imudp. Thanks to Anton for reporting this bug.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Most importantly, DNS resolution now never happens if the resolved name
is not required. Note that this applies to imudp - for the other inputs,
DNS resolution almost comes for free, so we do not do it there. However,
the new method has been implemented in a generic way and as such may
also be used by other modules in the future.
|
| |
| |
| |
| |
| |
| | |
primarily a problem of imdiag. Also added some fix for a potential
situation during cancel processing. That one is not considered vital
and may later be removed again.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
This was a recently introduced regression.
|