[rsyslog] abort cases

[Rainer Gerhards]

Please also read this:

http://kb.monitorware.com/post13847.html#p13847

It has some other interesting findings which leads me to believe I have
really found the culprit (or at least one of them ;)).

Feedback appreciated.

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Rainer Gerhards
> Sent: Thursday, September 18, 2008 9:35 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] abort cases
> 
> > 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.
> 
> Oh, I forgot, there is one thing you could actually do: I do not
intend
> to do any threading changes to the current stable. This may sound
> silly,
> because it looks like a bug, but I expect that a lot of changes need
to
> be done, especially to make helgrind happy (so that it can be used).
> The
> amount of changes I expect are far too intrusive for the stable. After
> all, the majority of folks do not experience the bug. So the "fix"
will
> become part of the current devel.
> 
> As such, it would be very useful for me if you could try out the
latest
> devel versions as I modify them. It would be really great if you could
> pull them from my git archive at git.adiscon.com/git/rsyslog.git
> 
> The same to everyone else interested in this work ;)
> 
> Rainer
> 
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog