| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
affected directive was: $ActionExecOnlyWhenPreviousIsSuspended on
|
| |
|
|\ |
|
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=203
|
| |
| |
| |
| |
| | |
Thanks to Peter Eisentraut for reporting and analysing this problem.
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=221
|
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=232
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
this could happen if multiple rulesets were used and some output batches
contained messages belonging to more than one ruleset.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=226
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=218
|
| |
| |
| |
| | |
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=225
|
| |
| |
| |
| | |
... what actually was a left-over. Java is no longer required.
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| | |
Under some circumstances an invalid truncation was detected. This
code has now been removed, a file change (and thus resent) is only
detected if the inode number changes.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This can happen when 0 bytes are read from the input file, and some
writer appends data to the file BEFORE we check if a rollover happens.
The check for rollover uses the inode and size as a criterion. So far,
we checked for equality of sizes, which is not given in this scenario,
but that does not indicate a rollover. From the source code comments:
Note that when we check the size, we MUST NOT check for equality.
The reason is that the file may have been written right after we
did try to read (so the file size has increased). That is NOT in
indicator of a rollover (this is an actual bug scenario we
experienced). So we need to check if the new size is smaller than
what we already have seen!
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- bugfix: action processor released mememory too early, resulting in
potential issue in retry cases (but very unlikely due to another
bug, which I also fixed -- only after the fix this problem here
became actually visible).
- bugfix: batches which had actions in error were not properly retried in
all cases
|
| |
| |
| |
| |
| |
| | |
circumstances
also fixed some cosmetic nits
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/parser.c
runtime/queue.c
runtime/wtp.c
template.c
threads.c
tools/syslogd.c
|
| | |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
plugins/imfile/imfile.c
runtime/stream.c
|
| | | |
| | | |
| | | |
| | | | |
namely Ubuntu (not their fault, but occured there)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Most importantly, this problem can not experienced on recent Fedora
64 bit OS (which has 64 bit long's!)
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
plus some minor nits. This was found after a clang static code analyzer
analysis (great tool, and special thanks to Marcin for telling me about
it!)
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
At least one instance of that problem could potentially lead
to abort (inside omfile).
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
configure.ac
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- added the $InputFilePersistStateInterval config directive to imfile
- changed imfile so that the state file is never deleted (makes imfile
more robust in regard to fatal failures)
|
| | | | | |
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | | |
Conflicts:
configure.ac
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... in a tight loop, effectively disabling functionality and bearing the
risk of unresponsiveness of the whole system.
Bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=194
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
epoll_create().
Bug: http://bugzilla.adiscon.com/show_bug.cgi?id=204
Thanks to Nicholas Brink for reporting this problem.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: http://bugzilla.adiscon.com/show_bug.cgi?id=206
Thanks to David Hill for alerting us.
|
| |_|/ /
|/| | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
Makefile.am
tests/tcpflood.c
|
| |\| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
runtime/stream.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- bugfix: a couple of problems that imfile had on some platforms, namely
Ubuntu (not their fault, but occured there)
- bugfix: imfile utilizes 32 bit to track offset. Most importantly,
this problem can not experienced on Fedora 64 bit OS (which has
64 bit long's!)
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
Makefile.am
configure.ac
runtime/rsyslog.h
tests/Makefile.am
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | | |
imptcp is a simplified, Linux-specific and potentielly fast
syslog plain tcp input plugin (NOT supporting TLS!)
|
| | | | | |
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
runtime/rsyslog.h
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
Makefile.am
configure.ac
doc/rsyslog_conf_modules.html
runtime/rsyslog.h
tests/Makefile.am
|