summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* rollback html editor rewrite of imfileRainer Gerhards2013-07-021-165/+230
|
* bugfix: double-free in omelasticsearchRainer Gerhards2013-07-022-1/+3
| | | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=461 Thanks to Marius Ionescu for providing a detailled bug report
* bugfix: in RFC5425 TLS, multiple wildcards in auth could cause segfaultRainer Gerhards2013-06-272-0/+2
|
* added "required" parameters, fixed conf snippet, bolded defaultsRadu Gheorghe2013-06-251-230/+165
|
* bugfix: omrelp potential segfault at startup on invalid config parametersRainer Gerhards2013-06-252-1/+3
| | | | | Conflicts: ChangeLog
* lmsig_gt: remove no longer needed error messageRainer Gerhards2013-06-251-2/+0
| | | | This is now properly handled inside rsyslog core.
* bugfix: lmsig_gt abort on invalid configuration parametersRisto Laanoja2013-06-252-2/+13
| | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=448
* imfile: remove redundant error mesageRainer Gerhards2013-06-251-2/+0
|
* testbench: "prevent" memleaks due to raceRainer Gerhards2013-06-251-0/+1
| | | | | | | | | | imdiag may not have enough time to properly terminate when the shutdown request is made. Thus we give it a little headroom. Note that this does not address a real issue inside the code - at most, it looks like a memory leak, but one where the whole process is immediately destructed. However, it is an annouance for the testbench. Note that the race may still occur based on circumstances, but now is much less likely.
* debug: add memleak info to "make distcheck"Rainer Gerhards2013-06-251-0/+1
| | | | | do --enable-valgrind to get better diagnostics in case of memory leaks
* build: fix issues on FreeBSDRainer Gerhards2013-06-253-3/+5
| | | | | The last fix was incomplete. Thanks to Christiano for testing and suggestions.
* doc: update ChangeLogRainer Gerhards2013-06-251-0/+2
|
* typo fix ("listner" vs. "listener")Michael Biebl2013-06-258-10/+10
|
* imtcp: permit parameter name with typo for backward compatibilityRainer Gerhards2013-06-251-1/+3
|
* imtcp: fix typo in config parameter nameMichael Biebl2013-06-251-2/+2
|
* bugfix: potential segfault on rsyslog termination in imudpRainer Gerhards2013-06-252-1/+2
| | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=456
* bugfix: RainerScript object required parameters were not properly checkedRainer Gerhards2013-06-244-10/+14
| | | | this clould result to segfaults on startup if parameters were missing.
* bugfix: omrelp "template" parameter is NOT requiredRainer Gerhards2013-06-241-1/+1
|
* $uptime property: fix mem leak and build problems on FreeBSDRainer Gerhards2013-06-242-3/+29
|
* solve build problem on FreeBSDRainer Gerhards2013-06-241-1/+5
| | | | Thanks to Christiano for reporting this problem.
* impstats: solve build problem on FreeBSDRainer Gerhards2013-06-242-0/+9
| | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=458
* imptcp: improve docRainer Gerhards2013-06-201-6/+6
|
* doc bugfix: invalid parameter nameRainer Gerhards2013-06-201-1/+1
|
* Add missing testMichael Biebl2013-06-201-1/+1
| | | | | Fixes ./configure: line 18474: xno: command not found
* doc: imjournal doc correctionTomas Heinrich2013-06-191-1/+1
|
* doc: remove duplicate omfile descriptionsRainer Gerhards2013-06-171-38/+34
| | | | | always bears the risk that one or another is not maintained when an update happpens
* prepare for 7.4.1 releasev7.4.1Rainer Gerhards2013-06-173-3/+3
|
* imjournal: rate limiter was destructed too earlyRainer Gerhards2013-06-171-1/+1
| | | | | Too quick hacking, obviously, one too late, one too early, now it should fit ;) Thanks to Tomas Heinrich for pointing this out.
* imjournal fix: put ratelimiter destruction in wrong entry pointRainer Gerhards2013-06-172-2/+2
| | | | No regression, this was in recently written, never-released code.
* implement new ratelimiting mode for imjournalRainer Gerhards2013-06-173-1/+20
| | | | | | | | | | | | | 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 ;)
* doc: legacy parameter description in imjournal slightly wrongRainer Gerhards2013-06-171-2/+2
|
* doc cleanupRainer Gerhards2013-06-171-5/+5
|
* Add IgnorePreviousMessages option to imjournal.Milan Bartos2013-06-172-9/+41
| | | | | | | | | | | | | This option specifies whether imjournal should ignore messages that are currently in journal. This option is only used when there is no StateFile to avoid message loss. modified: doc/imjournal.html modified: plugins/imjournal/imjournal.c Conflicts: doc/imjournal.html plugins/imjournal/imjournal.c
* doc: improve imjournal docRainer Gerhards2013-06-171-17/+19
| | | | most importantly, convert sample to new-style config format
* fix imjournal doc after merging patchRainer Gerhards2013-06-171-11/+2
| | | | | ... was changed in the interim, so the result of the merge was sub-optimal ;)
* Merge branch 'tmp' into v7-stableRainer Gerhards2013-06-172-3/+14
|\ | | | | | | | | Conflicts: plugins/imjournal/imjournal.c
| * Rename legacy imjournal configs to have "imjournal" prepended.Milan Bartos2013-06-172-3/+14
| | | | | | | | | | modified: doc/imjournal.html modified: plugins/imjournal/imjournal.c
* | doc bugfix: DynaFileCacheSize description in omfile was wrongRainer Gerhards2013-06-161-2/+6
| | | | | | | | thanks to David Lang for alerting me.
* | doc: add journal presentation link to omjournal docRainer Gerhards2013-06-161-0/+3
| |
* | doc: improve imjournal doc and add ratelimiting paramtersRainer Gerhards2013-06-161-8/+56
| |
* | imjournal: add legacy config statement for ratelimitingRainer Gerhards2013-06-151-0/+4
| |
* | imjournal: add ratelimiting capabilityRainer Gerhards2013-06-152-8/+32
| | | | | | | | | | | | | | | | | | | | | | The original imjournal code did not support ratelimiting at all. We now have our own ratelimiter. This can mitigate against journal database corruption, when the journal re-sends old data. This is a current bug in systemd journal, but we won't outrule this to happen in the future again. So it is better to have a safeguard in place. By default, we permit 20,000 messages witin 10 minutes. This may be a bit restrictive, but given the risk potential it seems reasonable. Users requiring larger traffic flows can always adjust the value.
* | doc: warn about using imjournalRainer Gerhards2013-06-151-0/+8
| | | | | | | | do to bugs in systemd, the module can lead to a DoS to the local machine
* | doc: mention contributed patch in ChangeLogRainer Gerhards2013-06-141-0/+1
| |
* | bugfix: prevent a segfault if state file is not definedTomas Heinrich2013-06-141-12/+31
| |
* | systemd: use service type notifyCristian Rodríguez2013-06-142-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a time window, between rsyslog reporting syntax errors and the daemon returning with failure, this may cause systemctl restart rsyslog to not report any error inmediately but later in the logs which is confusing to users. The appropiate steps to correct this annoyance is to notify systemd with a simple sd_notify(0, "READY=1"); just before entering the main loop. Tested in openSUSE 12.3/13.1 x86_64
* | Fix rsyslog.service to comply with systemd recommendationsCristian Rodríguez2013-06-141-1/+1
| | | | | | | | | | | | Those are documented here: http://www.freedesktop.org/wiki/Software/systemd/syslog/
* | bugfix: prevent calling tellLostCnt() twiceTomas Heinrich2013-06-121-1/+1
| |
* | bugfix: prevent another endless loop in the ratelimiterTomas Heinrich2013-06-121-1/+1
| | | | | | | | | | | | 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.
* | doc bugfix: imrelp does not have a v6+ "ruleset" config parameterRainer Gerhards2013-06-101-4/+2
| |