| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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
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:
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
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
LocalDomain points to "" or the domain in LocalHostName,
allocate as new string before passing to SetLocalDomain
or free will fail later.
Signed-off-by: Marius Tomaschewski <mt@suse.com>
|
| | | |
| | | |
| | | |
| | | | |
Thanks to Marius Tomaschewski for reporting this bug.
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
configure.ac
doc/manual.html
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/imuxsock.html
doc/manual.html
runtime/queue.c
|
|\ \ \ \ \
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
action.c
configure.ac
doc/imuxsock.html
plugins/imklog/imklog.c
plugins/imptcp/imptcp.c
plugins/imtcp/imtcp.c
plugins/imudp/imudp.c
plugins/imuxsock/imuxsock.c
runtime/glbl.c
runtime/glbl.h
runtime/net.c
runtime/ruleset.c
tcpsrv.h
tools/syslogd.c
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | | |
Conflicts:
configure.ac
|
| | |_|/
| |/| |
| | | |
| | | |
| | | | |
... for locally originating messages. New directive $LocalHostIPIF.
Note that not all modules yet support this new directive - next step...
|
| | | |
| | | |
| | | |
| | | | |
new config directives: $IMUXSockLocalIPIF
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
$MainMsgQueueLightDelayMark, $ActionQueueLightDelayMark; both
specify number of messages starting at which a delay happens.
|
|\ \ \ \ |
|
| |\ \ \ \
| | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |/ / |
|
| | | | |
|
| | | | |
|