| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Thanks to Andre Lorbach for mentioning this.
|
|\
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| |
| |
| |
| | |
some more elaborate patch is needed and will be provided
|
| | |
|
| |
| |
| |
| |
| | |
... it could pass a NULL pointer to unlink. Depending on OS implementation,
this could (or could not...) lead to a segfault.
|
| |
| |
| |
| |
| | |
...due to invalid mutex synchronisation in DA worker. In case of
idle queue, mutex was incorrectly locked.
|
| |
| |
| |
| | |
This is done to prevent name claches with libraries.
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| | |
Thanks to Zdenek Salvet for finding this bug and to Bodik for reporting
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/modules.c
|
| |
| |
| |
| |
| |
| | |
If it is not present, it must have the nilvalue "-" as of RFC5424
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=332
Thanks to John N for reporting this issue.
|
| |
| |
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=316
Thanks to Andreas Piesk for reporting&analyzing this bug as well as
providing patches and other help in resolving it.
|
| |
| |
| |
| | |
also added some error checking
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
runtime/queue.c
|
| |
| |
| |
| |
| | |
This is a minor optimization to spare some cycles if the timeout
is set to immediate discard
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and
full delayable sources somewhat smarter and permits, assuming sufficient
timouts, to persist message up to the max queue capacity. Also some nits
in debug instrumentation have been fixed.
|
| |
| |
| |
| |
| |
| |
| |
| | |
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and
full delayable sources somewhat smarter and permits, assuming sufficient
timouts, to persist message up to the max queue capacity. Also some nits
debug instrumentation have been fixed.
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |
| |
| |
| |
| |
| |
| | |
...due to unvailable sources. Fixes:
http://bugzilla.adiscon.com/show_bug.cgi?id=299
Thanks to Marcin M for bringing up this problem and Andre Lorbach
for helping to reproduce and fix it.
|
| |
| |
| |
| |
| |
| | |
While this is a bug, we assume it did have no practical effect
because the reset as it was done was set to the state the code actually
had at this point. But better fix this...
|
| |
| |
| |
| | |
at least for prolonged period of time...
|
|\ \ |
|
| |/ |
|
| |
| |
| |
| |
| | |
actually a regression from last bugfix - I just wonder why the other
machine did not complain :-S
|
|\ \ |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/msg.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
This looked quite hard to diagnose for disk-assisted queues, as the
pure memory part worked well, but ruleset info was lost for messages
stored inside the disk queue.
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imuxsock/imuxsock.c
runtime/glbl.c
|
| | |
| | |
| | |
| | | |
Signed-off-by: Marius Tomaschewski <mt@suse.com>
|
| | |
| | |
| | |
| | | |
Thanks to Marius Tomaschewski for reporting this bug.
|
| | |
| | |
| | |
| | | |
Thanks to Jo Rhett for the suggestion.
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
configure.ac
doc/manual.html
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
configure.ac
|
| | |
| | |
| | |
| | |
| | |
| | | |
queue config
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | |
| | | |
with the exception of imdiag, which I humbly do not think needs this
capabilit (even counter-productive for testbench use).
|
| | |
| | |
| | |
| | |
| | | |
... for locally originating messages. New directive $LocalHostIPIF.
Note that not all modules yet support this new directive - next step...
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
configure.ac
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imuxsock/imuxsock.c
runtime/queue.c
runtime/queue.h
|
| | | |
|