rsyslog.git - rsyslog development for Lumberjack - various unofficial and potentially rebased branches

	Commit message (Collapse)	Author	Age	Files	Lines
*	bugfix: fixed a memory leak and potential abort condition	Rainer Gerhards	2011-02-25	1	-1/+7
\| \| \| \| \| \| \|	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 fixes in action processing	Rainer Gerhards	2010-12-17	1	-3/+8
\| \| \| \| \| \| \| \| \|	- 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
*	made hardcoded max string number persistent	Rainer Gerhards	2010-06-24	1	-5/+3
\| \| \| \|	see commit for reasoning
*	bugfix: "$ActionExecOnlyWhenPreviousIsSuspended on" was broken	Rainer Gerhards	2010-06-24	1	-0/+19
\| \| \| \| \| \| \| \| \|	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.
*	milestone(BUGGY): batch now pushed down to action	Rainer Gerhards	2010-06-15	1	-1/+72
\| \| \| \| \| \| \|	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 processing	Rainer Gerhards	2010-06-10	1	-0/+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.
*	some cleanup	Rainer Gerhards	2010-06-10	1	-0/+6
\| \| \| \| \|	as well as some work in preparation of storing doAction params inside the batch
*	implemented solution for cancel at shutdown/unprocessed entries	Rainer Gerhards	2009-10-26	1	-1/+1
\| \| \| \| \|	We do now enqueue those objects that are left unprocessed. This enables us to delete the full batch, what is exactly what we need to do.
*	solved the intended-discard-during-dequeue issue	Rainer Gerhards	2009-05-19	1	-0/+6
\|
*	t-delete list implemented, queue store drivers updated...	Rainer Gerhards	2009-05-18	1	-0/+1
\| \| \| \| \| \|	... on the way to the ultra-reliable queue modes (redesign doc). This version does not really work, but is a good commit point. Next comes queue size calculation. DA mode does not yet work.
*	action batch processing implemented	Rainer Gerhards	2009-05-12	1	-1/+3
\| \| \| \|	... passed initial tests, but of course more are needed
*	moving to a cleaner implementation of batches	Rainer Gerhards	2009-05-12	1	-0/+63
	... now that we know what we need from a theoretical POV.