| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
this was due to improper parsing of ":"
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=250
|
| |
|
|
|
|
|
|
| |
even on platforms that place a low limit on the number of
file descriptors per processes. The tool now increases the
fd limit as required.
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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!
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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!)
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
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
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- 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!)
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
doc/professional_support.html
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/conf.c
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
they are now dropped as they always should have been
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
thanks to Anthony Edwards for pointing the problems out
|
| | | |
|
| | |
| | |
| | |
| | | |
testbench
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This, in default mode, caused buffered writing to be used, what
means that it looked like no output were written or partial
lines. Thanks to Michael Biebl for pointing out this bug.
|
| | |
| | |
| | |
| | | |
to test robustness
|
| | |
| | |
| | |
| | |
| | |
| | | |
...message-induced off-by-one error (potential segfault) (see 4.6.2)
The analysis has been completed and a better fix been crafted and
integrated.
|
| | |
| | |
| | |
| | |
| | | |
accidently, the time zone information was kept inside some
to-be-checked-for responses
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
a3e48b697fa664110567fcd0027d24ea5a239041
... so that the testbench continues to work
|
| | |
| | |
| | |
| | | |
it permits to specifiy if asynchronous writing should be done or not
|
| | |
| | |
| | |
| | |
| | | |
some versions of autotools seem to require it. The file itself is NOT
of interest for the project
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Further testing turned out that the rsyslog core works correctly and
this fix is not needed. The concurrency we saw was actually caused by
other actions (even processes) during directory creation. See commit
9e5b31fc44136dbcc1e443cfe7714e9daf97d844 for further details.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some types of malformed messages could trigger an off-by-one error
(for example, \0 or \n as the last character, and generally control
character escaption is questionable). This is due to not strictly
following a the \0 or string counted string paradigm (during the last
optimization on the cstring class). As a temporary fix, we have
introduced a proper recalculation of the size. However, a final
patch is expected in the future. See bug tracker for further details
and when the final patch will be available:
http://bugzilla.adiscon.com/show_bug.cgi?id=184
Note that the current patch is considered sufficient to solve the
situation, but it requires a bit more runtime than desirable.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This bug was triggered by an open failure. The the cache was full and
a new entry needed to be placed inside it, a victim for eviction was
selected. That victim was freed, then the open of the new file tried. If
the open failed, the victim entry was still freed, and the function
exited. However, on next invocation and cache search, the victim entry
was used as if it were populated, most probably resulting in a segfault.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If multiple files try to create a directory at (almost) the same time,
some of them may fail. This is a data race and also exists with other
processes that may create the same directory. We do now check for this
condition and gracefully handle it.
|