| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
action.c
queue.c (some code moved from action.c --> queue.c)
|
| | |
|
|\| |
|
| |
| |
| |
| |
| | |
it now truncates these message, but ensures they are sent. Note that
7.2.5+ will switch to fragmented UDP messages instead (up to 64K)
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This happened only on very high volume systems, if the same message was
being processed by two different actions. This was a regression caused
by the new config processor, which did no longer properly enable msg
locking in multithreaded cases. The bugfix is actually a refactoring of
the msg locking code - we no longer do unlocked operations, as the use
case for it has mostly gone away. It is potentially possible only at
very low-end systems, and there the small additional overhead of doing
the locking does not really hurt. Instead, the removal of that
capability can actually slightly improve performance in common cases,
as the code path is smaller and requires slightly less memory writes.
That probably outperforms the extra locking overhead (which in the
low-end case always happens in user space, without need for kernel
support as we can always directly aquire the lock - there is no
contention at all).
|
| |
| |
| |
| | |
which could also mean "never" or "not for a very long time".
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note: this was not a simple merge, I rather needed to adopt the v5 code to
the new v6 config handling. However, no v6 config format has been added yet
(this is the next step).
Conflicts:
plugins/imklog/imklog.c
plugins/imklog/imklog.h
|
| |
| |
| |
| |
| |
| | |
... actually, they are microseconds. So the fractional part of the
timestamp was not properly formatted.
Thanks to Marius Tomaschwesky for the bug report and the patch idea.
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
|\| | |
|
| | | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
both from code & doc and emitted warning message if still used
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=361
Thanks to Michael Biebl for reporting & suggestions
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imuxsock/imuxsock.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This happened only under some circumstances. Thanks to Marius
Tomaschwesky, Florian Piekert and Milan Bartos for their help in
solving this issue.
Note that Milan sent a patch, which solved the problem under some
conditions (can be found somewhat earlier in git history). However,
it did not handle the original root cause, and so did not fix the
problem always. The main reason was that the date parser modifies
the provided lenghts. That part of the API was not properly
used by the caller (who decremented the length once more).
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
CEE originally specified the cookie with SP, whereas other lumberjack
tools used it without space. In order to keep interop with lumberjack,
we now use the cookie without space as well. I hope this can be changed
in CEE as well when it is released at a later time.
Thanks to Miloslav Trmač for pointing this out and a similiar v7 patch.
|
| | | |
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for identifying this as the culprit for
several build-related issues. The plugin is a placeholder, and was
not used for quite some while. It is definitely not worth the effort
to keep it along. If needed, can be quickly created.
|
|\| | |
|
| | | |
|
| | | |
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
The problem occured when using the -f (dynafiles) option,
and caused some tests to fail.
|
| | |
| | |
| | |
| | | |
This could lead to startup with invalid parameters.
|
| | | |
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imrelp/imrelp.c
|