| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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".
|
|
|
|
|
| |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
|\| |
|
| |
| |
| |
| | |
libtool archives are not meant to be shipped in the source tarball.
|
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
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.
|
| | |\ \ |
|
| |\ \ \ \
| | | |_|/
| | |/| | |
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | | |
note that none of the rsyslog-provided plugins does this
Thanks to bodik and Rohit Prasad for alerting us on this bug and
analyzing it.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=347
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Thanks to bodik for reporting this bug.
---------------------------------------------
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
runtime/rsyslog.h
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The interface was actually not present in older versions, even though some modules
already used it. The implementation was now done, and not in 6.3/6.4
because the resulting memory leak was ultra-slim and the new interface
handling has some potential to seriously break things. Not the kind of
thing you want to add in late beta state, if avoidable.
|
| | | | |
| | | | |
| | | | |
| | | | | |
some nits to iron out, only omfile actually support module params
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(should originally have this value; larger value makes limited sense
giving current batch sizes)
|
| | | | | |
|
|\| | | | |
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | | |
Conflicts:
runtime/modules.c
|
| | |\ \ \
| | | | |/
| | | |/|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/modules.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There seem to be cases where the shutdown message is otherwise not
processed, not even on an idle system. Thanks to Marcin for
bringing this problem up.
|
|\| | | | |
|
| |\| | | |
|
| | |\| |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
runtime/queue.c
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Now it's probably time to prove the effect in practice...
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
This actually at compile time disables a lot of debug code, resulting
in some speedup (but serious loss of debugging capabilities)
|
|\| | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|