>From my POV the real issue is that there is very much going on at the moment
(I don't want to complain about that). But that also means I need to
prioritize the things I do. While I would like to have bugfixing always on
top of the list, it is plain truth that there are also some other factors
(like how to obtain bread for breakfast ;)), so priorities are also dictated
by commercial activities that need to run alongside. 

As a reminder, rsyslog development is still very largely depending on Adiscon
funding and that also means things like EventReporter actually pay for it
(some people may think well about that fact and its implications ;)). If I
worked on rsyslog just as a byline hobby activity, we were nowhere close to
where we are right now. But, as I said: the bottom line is that priorities
come with a twist of "as time permits".

Anyhow, I am quite concerned about this bug and hope to be able to look at it
as soon as possible. As another side-node running development versions and
providing good bug reports is also an excellent way to contribute to the
project... If you followed the mailing list, my priority scheme also slightly
involves that bug reports/feature whishes from those that contribute
frequently have a somewhat higher priority than from those who do not. I find
this is only fair. 

Rainer

> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of Mr. Demeanour
> Sent: Sunday, November 08, 2009 6:24 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] Rsyslog 4.4.2: server out-of-memory with gnutls
> 
> Rainer Gerhards wrote:
> > Thanks, but I wasn't specific enough. For TLS, I also need to client
> > config, because I need two machines to reproduce any issues (these
> > two instances are also the challenge for the current testbench, what
> > requires hopefully fewer than I expect changes ;)).
> 
> Perhaps someone could advise me on an alternative to resolving this
> problem by means of bug-hunting. While 4.4.2 is the version of rsyslog
> currently shipping in Debian squeeze, it's obviously a bit out-of-date
> from the point of view of the developers.
> 
> Well, the reason I'm using that version is precisely that it ships with
> Debian. Or to be more precise, I upgraded to squeeze because it ships
> with a version of rsyslog that includes encryption support. So perhaps
> I
> should just cut free, and install 5.x stable?
> 
> --
> Jack.
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to