summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* asigned special build numberv4.6.4-a1Rainer Gerhards2011-05-203-2/+4
|
* bugfix: invalid processing in QUEUE_FULL conditionRainer Gerhards2011-05-202-2/+16
| | | | | | | | | | | | If the the multi-submit interface was used and a QUEUE_FULL condition occured, the failed message was properly destructed. However, the rest of the input batch, if it existed, was not processed. So this lead to potential loss of messages and a memory leak. The potential loss of messages was IMHO minor, because they would have been dropped in most cases due to the queue remaining full, but very few lucky ones from the batch may have made it. Anyhow, this has now been changed so that the rest of the batch is properly tried to be enqueued and, if not possible, destructed.
* fixed memleak on queue fullRainer Gerhards2011-05-191-1/+1
|
* more information on TCP abort (tcp input)Rainer Gerhards2011-05-191-3/+5
|
* hardcoded: tcp input data is non-delayableRainer Gerhards2011-05-191-1/+1
|
* imptcp: added $InputPTCPServerAddtlFrameDelimiter directiveRainer Gerhards2010-08-118-12/+78
| | | | also improved testbench
* fixed minor issue: imptcp did a close(-1) on each acceptRainer Gerhards2010-08-111-1/+2
|
* imptcp: added $InputPTCPServerNotifyOnConnectionClose directiveRainer Gerhards2010-08-112-8/+8
| | | | plus some minor cleanup
* more testbench improvements and new testsRainer Gerhards2010-08-106-58/+107
|
* small improvements to testbenchRainer Gerhards2010-08-102-1/+3
|
* some cleanup and minor optimizationRainer Gerhards2010-08-101-33/+32
|
* added tests for imptcp and fixed some problems with itRainer Gerhards2010-08-105-19/+78
| | | | it now also works reliably in edge-triggered mode
* added imptcpRainer Gerhards2010-08-1010-3/+1267
| | | | | imptcp is a simplified, Linux-specific and potentielly fast syslog plain tcp input plugin (NOT supporting TLS!)
* preparing for 4.6.4v4.6.4Rainer Gerhards2010-08-053-3/+3
|
* Merge branch 'v3-stable' into v4-stableRainer Gerhards2010-08-054-117/+4
|\ | | | | | | | | | | | | | | Conflicts: ChangeLog configure.ac doc/manual.html doc/professional_support.html
| * preparing for 3.22.2v3.22.2Rainer Gerhards2010-08-055-94/+5
| |
* | Merge branch 'v3-stable' into v4-stableRainer Gerhards2010-08-052-1/+5
|\| | | | | | | | | Conflicts: runtime/conf.c
| * program name filter ! in the configuration cannot be resetKiss Gabor (Bitman)2010-08-052-2/+3
| | | | | | | | Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
* | bugfix: zero-sized (empty) messages were processed by imtcpRainer Gerhards2010-07-282-2/+11
| | | | | | | | they are now dropped as they always should have been
* | bumped version numberRainer Gerhards2010-07-071-0/+2
| |
* | preparing for 4.6.3v4.6.3Rainer Gerhards2010-07-073-3/+3
| |
* | bugfix: segfault on HUP when "HUPIsRestart" was set to "on"varmojfekoj2010-07-052-0/+3
| | | | | | | | Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
* | some doc fixes; incorrect config samples could cause confusionRainer Gerhards2010-05-203-3/+4
| | | | | | | | thanks to Anthony Edwards for pointing the problems out
* | solving a number of minor (but annoying) issues in the build systemRainer Gerhards2010-04-126-9/+10
| |
* | added new configure option that permits to disable and enable an extended ↵Rainer Gerhards2010-04-124-2/+27
| | | | | | | | testbench
* | doc bugfix: $OMFileFlushOnTXEnd wrongly documentedRainer Gerhards2010-04-071-2/+2
| |
* | bugfix: default for $OMFileFlushOnTXEnd was wrong ("off").Rainer Gerhards2010-04-072-2/+7
| | | | | | | | | | | | 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.
* | improvded testbench: added test with truly random data received via syslog ↵Rainer Gerhards2010-04-017-36/+284
| | | | | | | | to test robustness
* | temporary bugfix replaced by permanent one for...Rainer Gerhards2010-03-315-17/+25
| | | | | | | | | | | | ...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.
* | bugfix: testbench failed when not executed in UTC+1 timezoneRainer Gerhards2010-03-295-5/+12
| | | | | | | | | | accidently, the time zone information was kept inside some to-be-checked-for responses
* | preparing for 4.6.2v4.6.2Rainer Gerhards2010-03-264-5/+4
| |
* | $OMFileAsyncWriting directive did not work properlyRainer Gerhards2010-03-251-1/+1
| |
* | disable testcases affected by temporary bugfix in commit ↵Rainer Gerhards2010-03-252-9/+13
| | | | | | | | | | | | a3e48b697fa664110567fcd0027d24ea5a239041 ... so that the testbench continues to work
* | new feature: $OMFileAsyncWriting directive addedRainer Gerhards2010-03-2520-35/+91
| | | | | | | | it permits to specifiy if asynchronous writing should be done or not
* | minor: add INSTALL file to gitRainer Gerhards2010-03-251-0/+365
| | | | | | | | | | some versions of autotools seem to require it. The file itself is NOT of interest for the project
* | undo experimental commit dccadb677c5a6b8379f631e4c1f14c8c4089d4a6Rainer Gerhards2010-03-251-9/+0
| | | | | | | | | | | | | | 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.
* | bugfix(temporary): message-induced off-by-one error (potential segfault)Rainer Gerhards2010-03-252-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | bugfix: potential segfault in dynafile cacheRainer Gerhards2010-03-252-1/+8
| | | | | | | | | | | | | | | | | | 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.
* | bugfix: race condition during directory creationRainer Gerhards2010-03-252-6/+31
| | | | | | | | | | | | | | 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.
* | streamline dynafile cache entry deletion a bitRainer Gerhards2010-03-232-9/+8
| | | | | | | | | | | | The old code looks a bit "strange", though not necessarily incorrect. The new code looks correct and is probably less irritating during bug hunting.
* | bugfix: potential re-use of free()ed file stream object in omfileRainer Gerhards2010-03-233-8/+27
| | | | | | | | | | | | | | when dynaCache is enabled, the cache is full, a new entry needs to be allocated, thus the LRU discarded, then a new entry is opend and that fails. In that case, it looks like the discarded stream may be reused improperly (based on code analysis, test case and confirmation pending)
* | adding testcase files missing in gitRainer Gerhards2010-03-232-0/+102
| |
* | valgrand accidently left enabled in diag.sh with the last commitRainer Gerhards2010-03-221-1/+1
| |
* | cleanup: removed no longer needed variableRainer Gerhards2010-03-221-3/+0
| | | | | | | | Most importantly, this keeps the thread debugger output clean.
* | bugfix(minor): BSD_SO_COMPAT query function had some global vars not ↵Rainer Gerhards2010-03-224-5/+10
| | | | | | | | | | | | | | properly initialized. However, in practice the loader initializes them with zero, the desired value, so there were no actual issue in almost all cases.
* | added one more test case for dynafile cacheRainer Gerhards2010-03-223-1/+55
| |
* | cleanup of debug message in testbenchRainer Gerhards2010-03-221-1/+0
| |
* | previous (experimental) patch was somewhat incorrect, fixedRainer Gerhards2010-03-221-1/+1
| | | | | | | | This is what caused the new test to fail...
* | added testcase showcasing problems when dynafile can not be openedRainer Gerhards2010-03-223-16/+75
| | | | | | | | | | note that so far no patch is provided. This has not yet been made part of "make check"
* | exp: made omfile ensure that it is not called twice in parallel on the same ↵Rainer Gerhards2010-03-211-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | file instance In theory, the rsyslog core should never call in parallel into an output module for the same instance. However, it looks like this seems to happen under (strange?) circumstances. I have now enhanced omfile so that it guards itself against being called in parallel on the same instance data. This is done to help troubleshooting and may stay as an interim solution if it proves to solve an anomaly we see in at least one installation (to trigger this problem, an extremely large traffic volume is needed).
generated by cgit (git 2.34.1) at 2024-04-27 03:08:04 +0000