| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
this could lead to loss of the repeated message content. As a side-
effect, it could probably also be possible that some segfault occurs
(quite unlikely). The root cause was that some counters introduced
during the malloc optimizations were not properly duplicated in
MsgDup(). Note that repeated message processing is not enabled
by default.
|
|\ |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
doc/rsyslog_conf.html
|
| | |
| | |
| | |
| | | |
in doc set (require TLS drivers)
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A comparison was done between the current and the former source address.
However, this was done on the full sockaddr_storage structure and not
on the host address only. This has now been changed for IPv4 and IPv6.
The end result of this bug could be a higher UDP message loss rate than
necessary (note that UDP message loss can not totally be avoided due
to the UDP spec)
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
runtime/msg.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that the orginal (higher version) patch states this happens only
when debugging mode is turned on. That statement is wrong: if debug
mode is turned off, the message is not being emitted, but the division
by zero in the actual parameters still happens.
|
| | |
| | |
| | |
| | |
| | | |
This causes grief with all receivers.
Bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=147
|
| | |
| | |
| | |
| | | |
(thanks to Michael Biebl for his help!)
|
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- control character DEL was not properly escaped
- NUL and LF characters were not properly stripped if no control
character replacement was to be done
- NUL characters in the message body were silently dropped (this was
a regeression introduced by some of the recent optimizations)
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
... resulting in some message properties be populated with strings from
previous messages. This was caused by an improper predicate check.
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... thus causing them to be treated as TAG (this was a regression
introduced from the "rfc3164 strict" change in 4.5.0).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In async write mode, we use modular arithmetic to index the output
buffer array. However, the counter variables accidently were signed,
thus resulting in negative indizes after integer overflow. That in turn
could lead to segfaults, but was depending on the memory layout of
the instance in question (which in turn depended on a number of
variables, like compile settings but also configuration). The counters
are now unsigned (as they always should have been) and so the dangling
mis-indexing does no longer happen. This bug potentially affected all
installations, even if only some may actually have seen a segfault.
|
| | | |
| | | |
| | | |
| | | | |
permits to specify how many TCP servers shall be possible (default is 20).
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Some devices seem to create them and I do not see any harm in supporting that.
|
| | | |
| | | |
| | | |
| | | | |
v4-beta was so far unreleased, so it was a bug only here
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...after sending n messages (actually, it re-opens the connection, the
name is used because this is a concept very similiar to
$ActionUDPRebindInterval). New config directive $ActionSendTCPRebindInterval
added for the purpose. By default, rebinding is disabled. This is considered#
useful for load balancers.
|
|\ \ \ \ \
| |_|/ / /
|/| | / /
| | |/ /
| |/| |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
tests/Makefile.am
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
We are doing this to support removal of restart-type HUP in v5.
Elaborate doc added to explain reasoning and actions to be taken.
|
| | | | |
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
(double free)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was a result of an internal processing error if maximum field
sizes had been specified in the property replacer.
Also did some testbench improvements, including omstdout.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
... when working with disk queues.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
(depending on configuration). This was a small change, but with big
results. There is more potential to explore, but the effects were so
dramatic that I think it makes sense to include this fix.
|
| | | |
| | | |
| | | |
| | | | |
Happend e.g. with imuxsock.
|
| | | |
| | | |
| | | |
| | | | |
...which permits to set a new console log level while rsyslog is active
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This could lead to timestamps written in the wrong format, but not to
an abort.
|
|\ \ \ \ |
|
| |\| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | |
|
| | | | | |
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
actually destructed.
This most likely had no effect to existing code, but it may also have
caused trouble in remote cases. Similarly, the fix may also cause trouble...
Due to this trouble scenario, the fix deserves its own commit.
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
tools/syslogd.c
|