[rsyslog] abort cases

[Lorenzo M. Catucci]

>> is still running, while it usually didn't last more than 12 hours, it
>> seems the timing variation does somewhat cure the symptoms.
>
> This is what I am thinking, too. I am running it under helgrind. If you
> do that, you'll see a couple of warnings, most have been found to be
> harmless by previous analysis. Anyhow, I am re-doing the analysis now
> (what takes quite a bit of time). I am just telling you so that you
> don't wonder when you see so many warnings. I think there is even a
> discussion thread somewhere telling why this is. Mostly it is cases
> where we do not really need sync... or so I thought ;)
>

Just to help me understand, do you think val-grinding this time is 
near-to-useless, and I'd better restart the daemon under helgrind, or you 
prefer I continue valgrinding while you helgrind?

I feared uttering the words "race condition" would have been doing just 
like the patient telling the doctor what he does want to hear as a 
dyagnosis... now that I see you are looking for missing syncs I think we 
share this gut feeling... Please let me know if I can help more, since 
I'm somewhat in the hope this dreaded shared memory 8 way system could 
very well shake the races... As a matter of fact, the destination server 
is a twin-brother of the source one, and is running (and logging to 
postgresql) without any hiccup since started-up.

Thank you very much, yours,

 	lorenzo