> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Tuesday, February 01, 2011 7:55 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 6.1.3 (v6-devel) released > > I was going to ask about that. I didn't realize that v6 was really > going > in new features, I thought it was just a testbed for the new config > parser > system.
It's both. I moved up to v6 because the config change is probably quite intrusive. But it *will* be the new main line, and so new features go into it (I usually branch within a release for purely experimental stuff). > > so two questions > > 1. should we be basing all new work on v6? > Ist probably a good idea, at least for major things. > 2. what happened about the config stuff? Well, our minimal consensus (action scoping) is in v6, but I did not get much feedback. I have begun to think that the minimal consensus is too minimal. I'd like to create at least an experimental completely new config parser with a cleaner and more powerful syntax. But there is quite some work in front of that. Unforutnately, the time window for changes to the config system closed last year when it became so unclear which direction to take. I hope it re-opens in spring, based on the other things that are going on. Maybe JSON would be an alternative -- liblognorm will probably need to support JSONish config for several reasons and if that works out, we could borrow there... Rainer > > David Lang > > On Tue, 1 Feb 2011, Rainer Gerhards wrote: > > > Hi David, > > > > thanks for putting this straight. It was actually my fault not to > tell Tom > > this for v6. I think the release cycle was a bit too long, too many > new > > features. I also think I need to concentrate on v6 now for new > features -- > > going back and forth between v5 and v6 for development releases is > sometimes > > quite confusing, at least to me ;) > > > > Rainer > > > >> -----Original Message----- > >> From: [email protected] [mailto:rsyslog- > >> [email protected]] On Behalf Of [email protected] > >> Sent: Tuesday, February 01, 2011 6:36 PM > >> To: rsyslog-users > >> Subject: Re: [rsyslog] rsyslog 6.1.3 (v6-devel) released > >> > >> also since 6.1.2 there has been a bunch of work on the imfile > module, a > >> number of bug fixes, but also it gained the ability to deal with > some > >> multi-line logs in files, combining the lines into one log entry > before > >> processing the log message. > >> > >> Rainer did the heavy debugging work and I contributed the multi-line > >> capibility > >> > >> I think this was announced as part of a 5.x release, but in the 6.x > >> tree > >> this is the first release with these changes. > >> > >> David Lang > >> > >> > >> On Tue, 1 Feb 2011, Tom Bergfeld wrote: > >> > >>> Hi all, > >>> > >>> We have just released rsyslog 6.1.3, the new v6-devel. > >>> This release brings a number of enhancements. > >>> First of all, it provides exciting new functionality in the form or > >> an > >>> experimental MongoDB output plugin and various message parsers. The > >> latter > >>> greatly increases rsyslog's ability to common malformed syslog > >> message > >>> formats. Also, ommysql now allows a much more fine-grained control > >> over MySQL > >>> settings. > >>> Then, a number of performance enhancements are made available: both > >> imtcp and > >>> imptcp have an optimized code based and imptcp has been enhanced to > >> be able > >>> to run multiple input threads concurrently (the same is planned for > >> imtcp in > >>> the not so distant future). Also, imdup has now the capability to > run > >> at > >>> real-time priority, which greatly reduces the chance of message > loss. > >>> Finally, there are a couple of bug fixes inside this release. > >>> > >>> We are especially proud that some of the important new features > were > >>> contributed code: David Lang contributed the message parsers, > Victor > >> Pereira > >>> the experimental MongoDB module, Dra?en Ka?ar the imudp realtime- > >> support and > >>> Ariel P. the enhancements for ommysql. Many thanks to all of you! > >>> > >>> Please see the ChangeLog for more details. > >>> > >>> ChangeLog: > >>> > >>> http://www.rsyslog.com/changelog-for-6-1-3-v6-devel/ > >>> > >>> Download: > >>> > >>> http://www.rsyslog.com/rsyslog-6-1-3-v6-devel/ > >>> > >>> As always, feedback is appreciated. > >>> > >>> Best regards, > >>> Tom Bergfeld > >>> -- > >>> > >>> Support > >>> > >>> ======= > >>> > >>> > >>> Improving rsyslog is costly, but you can help! We are looking for > >>> organizations that find rsyslog useful and wish to contribute back. > >> You can > >>> contribute by reporting bugs, improve the software, or donate money > >> or > >>> equipment. > >>> > >>> > >>> Commercial support contracts for rsyslog are available, and they > help > >> finance > >>> continued maintenance. Adiscon GmbH, a privately held German > >> company, is > >>> currently funding rsyslog development. We are always looking for > >> interesting > >>> development projects. For details on how to help, please see > >>> http://www.rsyslog.com/doc-how2help.html. > >>> _______________________________________________ > >>> 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 > > _______________________________________________ > > 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 _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
