| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Conflicts:
tools/syslogd.c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "queue.xxx" parameter set was not supported, and legacy ruleset
config statements did not work (by intention). The fix introduces the
"queue.xxx" parameter set. It has some regression potential, but only
for the new functionality. Note that using that interface it is possible
to specify duplicate queue file names, which will cause trouble. This
will be solved in v7.3, because there is a too-large regression
potential for the v7.2 stable branch.
|
| |
| |
| |
| |
| | |
the changes do not affect actual code execution, just keep the
compile log clean.
|
|\| |
|
| |
| |
| |
| | |
which could also mean "never" or "not for a very long time".
|
| | |
|
| |
| |
| |
| |
| | |
The indentation around the "-d" flag description is in the
wrong place and does not display properly.
|
| |
| |
| |
| |
| |
| | |
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.
|
|\| |
|
| |
| |
| |
| |
| | |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
| | |
|
| |\ |
|
| | | |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We also added a testbench test to check for this in the future. That
in turn required new testbench tools.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The most important real code chane is the initialization of the
epoll control set. This should just be cosmetic (valgrind warnings),
as all data we actually use already was properly initialized.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... because action-like statements in action lists are not supported
in 7.1. This will be available in 7.3, but it is too late to do this in
7.1. So we disable the warnings and re-enable them in 7.3. Functionality-
wise, this is no problem at all as the legacy constructs are still
fully supported.
Thanks to forum user "canadaboy" for mentioning this problem.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Thanks to Michael Biebl for mentioning this.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=364
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
Conflicts:
rsyslog.service.in
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
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/cust1/Makefile.am
|
| | |
| | |
| | |
| | | |
libtool archives are not meant to be shipped in the source tarball.
|
| | | |
|
|\ \ \
| | |/
| |/| |
|
| | | |
|
| | | |
|
|\| | |
|
| | | |
|
| | |
| | |
| | |
| | | |
... and used default template in all cases
|
| | |
| | |
| | |
| | |
| | | |
Thanks to Evgeny Turnaev for alerting us on the problem and
providing hits to the solution.
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsconf.c
|
| |\| |
|
| | |
| | |
| | |
| | | |
Interface needed to be changed in lower stream classes. Syslog TCP Sending is now resumed properly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
During config file processing, Omusrmsg often incorrectly returned a
warning status, even when no warning was present (caused by
uninitialized variable). Also, the core handled warning messages
incorrectly, and treated them as errors. As a result, omusrmsg
(most often) could not properly be loaded. Note that this only
occurs with legacy config action syntax. This was a regression
caused by an incorrect merge in to the 6.3.x codebase.
Thanks to Stefano Mason for alerting us of this bug.
|
| | | |
|
|/ / |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
runtime/ruleset.c
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
runtime/ruleset.c
template.h
threads.c
tools/syslogd.c
|
| | |\
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/ruleset.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This lead to queue file corruption. While the root cause is a config
error, it is a bug that this important and hard to find config error
was not detected by rsyslog.
|
| | | |
| | | |
| | | |
| | | | |
This is done to prevent name claches with libraries.
|