summaryrefslogtreecommitdiffstats
path: root/runtime/rule.c
Commit message (Collapse)AuthorAgeFilesLines
* bugfix: "$ActionExecOnlyWhenPreviousIsSuspended on" was brokenRainer Gerhards2010-06-241-22/+6
| | | | | | | | | Note that, as it looks, the directive was already broken in previous v5 versions. So while I solved what looked like a (intentional) regression from the performance tuning, I actually solved a previous regression as well ;) I have also added new test cases to the testbench in order to capture such problems in the future. This version does now look pretty good in shape.
* fixed a couple of regressionsRainer Gerhards2010-06-231-14/+3
| | | | | | | | by implementing some code that was missing so far ;) as well as finding some real bugs. I also did some general cleanup, removing debug strings and such. This code should be fairly OK to use, except when "exec only when previous action was suspended" is used -- this is NOT yet re-implemented in the tuned engine.
* milestone(BUGGY): batch now pushed down to actionRainer Gerhards2010-06-151-4/+7
| | | | | | | at least in important cases (not for non-direct action queues and some other minor things). This version is definitely buggy, but may be tried with success on a non-production system. I will continue to work on the correctness, but needed to commit now to get a baseline.
* milestone commit(BUGGY): batch is now handed down to rule processingRainer Gerhards2010-06-101-20/+28
| | | | | | | | Now, the full batch is passed down to the rule, which then enqueues the elements as single messages. Note that this code has some known defects and needs more changes until it is correct again. This is primarily a commit to be able to return to a known-(somewhat)-good state.
* main msg q consumer now preprocesses messages before doing rule processingRainer Gerhards2010-06-091-1/+0
| | | | | | | things like ACL check and message parsing. This leads to a greater level of concurrent processing. Beware, though, that this commit duplicates some messages. May be a regression from this or an earlier commit. I will soon sort out.
* added support for high-performance action queue submission if not all mark ↵Rainer Gerhards2010-06-081-1/+1
| | | | | | | | | | messages should be logged this was previously not properly handeld. This is also the first occurence of a (real) CAS loop inside rsyslog. Note that the performance is now very well in the default configuration, and mark message directives are still correctly being handled. So this code looks close to final, but needs to have some bug cleanup as the testsuite shows.
* Merge branch 'v4-stable' into tmpRainer Gerhards2010-03-011-0/+1
|\
| * cleanup: removed debug messages that accidently made it into the commitRainer Gerhards2010-03-011-0/+1
| |
* | some more cleanup along the wayRainer Gerhards2009-11-031-1/+29
| | | | | | | | ... getting the module structure a bit cleaner ;)
* | added new testcase; fixed bug in testdriverRainer Gerhards2009-10-191-0/+1
| |
* | reduced number of debug messages a bit againRainer Gerhards2009-08-261-2/+0
| |
* | bugfix: discard action did not work (did not discard messages)Rainer Gerhards2009-07-301-0/+2
|/
* small performance improvement and cleanupRainer Gerhards2009-07-091-3/+4
| | | | | | optimized substring processing, should bring a small enhancement when forwarding with the default forwarding templates. Also did some uchar cleanup in msg.c (thus so many changes, in reality they are few...).
* finished transition to using inputName propertyRainer Gerhards2009-06-301-4/+3
| | | | | ... plus some celanup and adding minor missing functionality (the rule debug info again tell the property name, not just number).
* optimization: propert names are now internally identified by integersRainer Gerhards2009-06-261-9/+5
|
* got rid of the recursive requirement for msg_t mutex (finally!)Rainer Gerhards2009-06-261-3/+4
|
* slight optimization of template generationRainer Gerhards2009-06-181-1/+3
|
* added $Ruleset config commandRainer Gerhards2009-06-101-0/+22
| | | | | | so we now can define multiple rule sets, we just can not use them ;) That means we have the foundation to bind listeners to different rule sets.
* fixed a small memory leak...Rainer Gerhards2009-06-101-3/+0
| | | | and another problem, both introduced today. Also did some general cleanup.
* restructered code in perparation for multiple rule set supportRainer Gerhards2009-06-101-0/+431
... this was long overdue, and I finlly tackeld it. It turned out to be more complex than I initially thought. The next step now probably is to actually implement multiple rule sets and the beauty that comes with them.