syslog-ng-announce

Download

syslog-ng-announce@lists.balabit.hu

January 2012

1 participants
2 discussions

Re: [syslog-ng-announce] [syslog-ng] syslog-ng 3.3.4 has been released
by BalaBit Development Team 22 Jan '12

22 Jan '12

On Fri, 2012-01-20 at 10:25 +0000, Dave Haywood wrote: > On 19/01/2012 18:51, devel(a)balabit.hu wrote: > > ------------------------------------------------------------------------------ > > PACKAGE : syslog-ng > > VERSION : 3.3.4 > > SUMMARY : new stable release > > DATE : Jan 19, 2012 > > ------------------------------------------------------------------------------ > > > > DESCRIPTION: > > > > A new stable version of syslog-ng Open Source Edition (3.3.4) has > > been > > released. For latest fixes in the 3.3.x feature branch you are > > recommended to > > upgrade to this version. > > I updated my local git tree and I don't see a tag for 3.3.4? > > $ git tag > v2.1.1 > v2.1alpha1 > v2.1beta1 > v2.1beta2 > v3.0.1 > v3.0.2 > v3.1.0 > v3.1beta1 > v3.1beta2 > v3.2alpha1 > v3.2beta1 > v3.3.0alpha1 > v3.3.0alpha2 > v3.3.0beta2 > v3.3.1 > v3.3.2 > > It would be really useful if you could tag it or post the commit ref > that 3.3.4 relates to? I did a "git pull" which, afaik, pulls the > tags too. > Did that, thanks. Seems my VPN connection wasn't alive when I did the release, thus it didn't get pushed. But I've now pushed all tags to both git.balabit.hu and github.com

1 0

syslog-ng 3.3.4 has been released
by devel＠balabit.hu 19 Jan '12

19 Jan '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.3.4 SUMMARY : new stable release DATE : Jan 19, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (3.3.4) has been released. For latest fixes in the 3.3.x feature branch you are recommended to upgrade to this version. CHANGES: 3.3.4 Mon, 16 Jan 2012 23:07:46 +0100 Highlights ========== This release is aimed fixing bugs in the 3.3.x series, with one more important change: there's an incompatible change in the processing of <action> tags in the db-parser() database format (aka patterndb), see below for more details. Bugfixes: ========= * Fixed set() and subst() rewrite operations to work properly on the value() parameter specified in the configuration even if they are referenced at multiple spots in the configuration file. Earlier the 2nd and subsequent invocation of the rewrite rule changed $MESSAGE. * Fixed csv-parser() to work even if it is invoked at multiple spots in the configuration file. Earlier, the 2nd and subsequent references of the parser rule forgot the list of column names and the input template. * Fixed the processing of condition() parameter in rewrite rules, which was broken if it contained a filter() function call. * Fixed program() destination to properly kill the child process on reload and shutdown. * Fixed a potential division by zero error which could happen for large data rates due to a race in an unlocked region. * Fixed an assertion failure in mongodb destination that happened due to a race condition at high data rates. * Fixed an fd leak in the control socket code, that caused the control connection file descriptors to be leaked. Other changes ============= * db-parser() automatically sets a tag named '.classifier.unknown' if the message doesn't match. * The use of actions in db-parser() for messages without a correllation context was inconsistently indexing messages. For actions in rules that had correllation @0 was the new message being generated, and @1 was the message that triggered the rule. Without correllation @0 was used for the triggering message, which is greatly inconsistent and unintuitive. This was fixed by changing the behaviour for rules without correllation, now both correllation and non-correllation rules use @0 for the new message, and @1 for the triggering message. This is an incompatible change in the db-parser() format. * The value of the $TAGS macro is added to pdbtool match output. * unix-dgram() and unix-stream() error logging on systemd failures became more detailed for easier troubleshooting. Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. These people have helped in this release: Attila M. Magyar (BalaBit) Balazs Scheidler (BalaBit) Costa Farber Dmitry Gilev Evan Rempel (University of Victoria) Fried Zoltan (BalaBit) Gergely Nagy (BalaBit) Jakub Jankowski (SuperHost.pl) John Morrissey (Horde.net) Michael Hocke (New York University) Michal Schmidt (RedHat) Peter Eisenlohr (Inform Software) Svante Signell (Telia.se) Thomas Wollner DOWNLOAD: You can download the source or binary packages from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at http://www.balabit.com/support/documentation/

1 0