| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/msg.c
runtime/queue.c
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
a special ratelimiter is used; it's linux-type ratelimit settings
are currently hardcoded
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Conflicts:
ChangeLog
doc/v7compatibility.html
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
no actual implementation yet done
|
|\ \ \ \ \ \ \ \ \
| | |_|_|_|_|/ / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Conflicts:
configure.ac
doc/manual.html
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
We also added a testbench test to check for this in the future. That
in turn required new testbench tools.
|
|\| | | | | | | |
| |_|_|_|_|/ / /
|/| | | | | | | |
|
| | | | | | | | |
|
|\| | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
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.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
merge for action list functionality will follow soon
|
|\| | | | | | |
| |_|_|/ / / /
|/| | | | | | |
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
... 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:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | | |
|
| | | | | | |
|
|\| | | | |
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | | |
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
|