| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/rsyslog.h
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Thanks to Jonny Törnbom for reporting this problem
Conflicts:
ChangeLog
runtime/cryprov.h
|
| |
| |
| |
| | |
Thanks to Michael Biebl for mentioning the problem.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The datatype of the argument to SetiMaxFileSize() was too small and
could overflow.
The SetMaxFileSize() interface wasn't used at all (possibly confused
with SetiMaxFileSize()) and was dropped.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
regression some time between v5 and here
Thanks to forum user rjmcinty for reporting this bug
|
| | | |
| | | |
| | | |
| | | |
| | | | |
regression from recent DA queue bug fix set of patches; not present
in any released code.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This was an extremely small one-time per run memleak, so nothing of
concern. However, it bugs under valgrind and similar memory debuggers.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The queue full loop fix added a problem to the queue when
rsyslog was shutdown. This problem has been corrected now.
Conflicts:
runtime/queue.c
|
| | | |
| | | |
| | | |
| | | | |
was introduced July, 5th 2013 by commit 8ee2b0b1610fbf4dff20453d188f379583410b42
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
This is now properly handled inside rsyslog core.
|
| | | |
| | | |
| | | |
| | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=448
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The last fix was incomplete. Thanks to Christiano for testing
and suggestions.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Thanks to Christiano for reporting this problem.
|
| | | |
| | | |
| | | |
| | | | |
No regression, this was in recently written, never-released code.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
and make imjournal use it.
The new mode is needed, as imjournal uses journal's timestamp
as message generation time (which otherwise is when the message
entered the system, and the ratelimiter uses this as current
timestamp in order to save performance).
It is debatable if imjournal is doing the right thing here. But
it doesn't feel totally wrong. So let's safe that debate for
later ;)
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The message that reports how many messages were lost due to
ratelimiting was sent before reseting the state that led to it. If it
itself got ratelimited, this could lead to an endless loop.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If messages are being dropped because of ratelimiting, an internal
message is generated to inform about this fact. This should happen
only uppon the firs occurance but the counter that tracks the number
of dropped messages was incremented only after sending the message. If
the message itself gets ratelimited, an endless loop spins out of
control. Thanks to Jerry James for notifying about this.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If multiple spaces were used in front of the template name, all but one
of them became actually part of the template name. So
$template a,"..." would be name " a", and as such "a" was not
available, e.g. in
*.* /var/log/file;a
This is a legacy config problem. As it was unreported for many years,
no backport of the fix to old versions will happen.
This is a long-standing bug that was only recently reported by forum
user mc-sim.
Reference: http://kb.monitorware.com/post23448.html
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This prevents linking with libee, liblognorm and libgcrypt when not
necessary.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Through msg.h, many unrelated components needlessly required
LIBEE_CFLAGS.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
init variable that does not really need to be initialized, as it
is immediately overwritten - but the compiler is not smart enough
to see that
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Now this triggers an error message and the queue is changed to
linkedList type.
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't want to hard-code `libgcrypt-config --libs` at various.
Also, make sure LIBGCRYPT_CFLAGS and LIBGCRYPT_LIBS are correctly
substituted.
|
| | | | |
| | | | |
| | | | |
| | | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=436
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
also max number of templates for plugin use has been increased to five
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=392
|