| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
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.
|
|\|
| |
| |
| |
| | |
Conflicts:
plugins/imrelp/imrelp.c
|
| | |
|
| |
| |
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=358
This happend to filters of the style "local0,local1.*", where the
multiple facilities were comma-separated.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This most importantly could happen due to configuration errors.
|
|\|
| |
| |
| |
| | |
Conflicts:
runtime/rule.c
|
| |
| |
| |
| |
| |
| | |
...if action chaining (& operator) was used
http://bugzilla.adiscon.com/show_bug.cgi?id=355
Thanks to pilou@gmx.com for the bug report
|
| |
| |
| |
| |
| |
| |
| | |
Only \' was supported. Now the usual set is supported. Note that v5
used \x as escape where x was any character (e.g. "\n" meant "n" and NOT
LF). This also means there is some incompatibility to v5 for well-know
sequences. Better break it now than later.
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
| | |
|
| |
| |
| |
| | |
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
action.c
configure.ac
doc/manual.html
runtime/ruleset.c
template.h
threads.c
tools/syslogd.c
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| |\|
| | |
| | |
| | |
| | | |
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.
|
| |\ \ |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
|
| | | | | |
|
|\ \ \ \ \
| | |_|_|/
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
some more elaborate patch is needed and will be provided
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\| | | | |
|
| | |_|/
| |/| |
| | | |
| | | |
| | | | |
...due to invalid mutex synchronisation in DA worker. In case of
idle queue, mutex was incorrectly locked.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Incremented pthread stack size to 4MB for imtcp, imptcp and imttcp
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=342
|
| | | | |
|
| | | | |
|