parser option in v2.1.3?
Is the parser option to split and work with the $MSG or $MSGONLY variables and split and use various fields from them in the destination filename available in the 2.1.3 tree or is this only available in the 3.x tree? Thank you, Shawn Saunders UNIX Systems Administrator 818.953.2649 WMG, Digital Properties "UNIX is user-friendly ... it's just selective about who its friends are!!"
On Wed, 2008-11-19 at 08:56 -0800, Saunders, Shawn wrote:
Is the parser option to split and work with the $MSG or $MSGONLY variables and split and use various fields from them in the destination filename available in the 2.1.3 tree or is this only available in the 3.x tree?
those are 3.0 features. -- Bazsi
Do you classify the 3.0 src as RC or Stable? Thank you, Shawn Saunders UNIX Systems Administrator 818.953.2649 WMG, Digital Properties "Who's General Failure and why's he reading my disk?" -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Wednesday, November 19, 2008 10:48 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] parser option in v2.1.3? On Wed, 2008-11-19 at 08:56 -0800, Saunders, Shawn wrote:
Is the parser option to split and work with the $MSG or $MSGONLY variables and split and use various fields from them in the destination filename available in the 2.1.3 tree or is this only available in the 3.x tree?
those are 3.0 features. -- Bazsi ________________________________________________________________________ ______ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
On Wed, 2008-11-19 at 11:17 -0800, Saunders, Shawn wrote:
Do you classify the 3.0 src as RC or Stable?
I have made no "official" releases of the 3.0 codebase yet, however nearly all of the functionality there comes from the Premium Edition, which has already been released as stable. I keep the two branches in sync manually, but the OSE tree is now up-to-date with regards to fixes in the PE version. There are occasional hiccups, like the compilation problem in your other e-mail. As I outlined in one of my previous e-mails, I'm in the process of changing the scripts performing the release as there are too many manual steps involved right now, which I get wrong from time to time. Once that is done, I can allocate some testers to do release testing and create an official release. But apart from these organizational issues, I consider the code in the git repository complete and stable, and I don't plan to break it in the nearfuture. :) Rather, I'd open a new branch instead, if I want to add new stuff. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Saunders, Shawn