| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\| | |
|
| | | |
| | | |
| | | |
| | | | |
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
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
if rsyslog was set to auto-background (thus fork, the default) and debug
mode to stdout was enabled, debug messages ended up in the first log file
opened. Currently, stdout logging is completely disabled in forking mode
(but writing to the debug log file is still possible). This is a change
in behaviour, which is under review. If it causes problems to you,
please let us know.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
(and template name set to "??" if the parameter was used)
Thanks to Brian Knox for alerting us on this bug.
|
| |_|/
|/| | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
tools/syslogd.c
|
| |\ \ |
|
| | |\|
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
plugins/imuxsock/imuxsock.c
runtime/glbl.c
|
| | | | |
|