------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.4.4 SUMMARY : new stable release DATE : Oct 17, 2013 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (3.4.4) has been released. For latest fixes in the 3.4.x feature branch you are recommended to upgrade to this version. CHANGES: 3.4.4 Thu, 17 Oct 2013 12:16:40 +0200 This is the third bug-fix release for the 3.4.x series, with important fixes over the 3.4.3 release. Upgrading to this release is highly recommended. Bugfixes ======== * Fixed the log message reference counting in the AMQP destination, thus stopping it from crashing. * Fixed a possible crash in the AMQP destination that could be triggered when the AMQP server was unreachable at the time of a syslog-ng reload or shutdown. * pdbtool no longer segfaults when used with the --module switch [#249] * pdbtool test exits with a return value of 2 if the test value matched a different pattern than expected. [#241] * The inherit-properties attribute was added to the patterndb XSD. [#251] * A memory corruption was fixed in the @STRING@ parser of db-parser(). [#254] * Corrected a mistake in the afsocket module that lead to crashes on reload when unix-stream or unix-dgram destinations were in use. * Excludes now work properly with value-pairs(), and they do not get ignored if the value to exclude is in the default set. * The program() source and destination now correctly kill the started child on reload and shutdown. * The file destination does not use lseek() anymore. * When setting default template options, all random memory junk is cleared from the object first. * The order of header include paths was fixed in the test suite, so it should compile cleanly even in the presence of potentially conflicting headers. Features ======== * The $(format-json) template function, and anything else that may use the same value-pairs command line parser now allow specifying multiple scopes separated by commas (as opposed to having to use the --scope switch multiple times) [#248] 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: Alexandre Biancalana <biancalana@gmail.com> Balazs Scheidler <bazsi@balabit.hu> Balint Kovacs <blint@balabit.hu> Evan Rempel <erempel@uvic.ca> Fabien Wernli <cpan@faxm0dem.org> Gergely Nagy <algernon@balabit.hu> Lucas McLane <lucas@clicksecurity.com> Marc Falzon <marc.falzon@cloudwatt.com> Michal Privoznik <miso.privoznik@gmail.com> Ryan Frederick Valentijn Sessink <valentijn@sessink.nl> 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/
looks like it's still using AM_CONFIG_HEADER(config.h) in modules/afmongodb/libmongo-client/configure.ac On Thu, Oct 17, 2013 at 7:48 AM, <devel@balabit.hu> wrote:
------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.4.4 SUMMARY : new stable release DATE : Oct 17, 2013 ------------------------------------------------------------------------------
DESCRIPTION:
A new stable version of syslog-ng Open Source Edition (3.4.4) has been released. For latest fixes in the 3.4.x feature branch you are recommended to upgrade to this version.
CHANGES:
3.4.4 Thu, 17 Oct 2013 12:16:40 +0200
This is the third bug-fix release for the 3.4.x series, with important fixes over the 3.4.3 release. Upgrading to this release is highly recommended.
Bugfixes ========
* Fixed the log message reference counting in the AMQP destination, thus stopping it from crashing.
* Fixed a possible crash in the AMQP destination that could be triggered when the AMQP server was unreachable at the time of a syslog-ng reload or shutdown.
* pdbtool no longer segfaults when used with the --module switch [#249]
* pdbtool test exits with a return value of 2 if the test value matched a different pattern than expected. [#241]
* The inherit-properties attribute was added to the patterndb XSD. [#251]
* A memory corruption was fixed in the @STRING@ parser of db-parser(). [#254]
* Corrected a mistake in the afsocket module that lead to crashes on reload when unix-stream or unix-dgram destinations were in use.
* Excludes now work properly with value-pairs(), and they do not get ignored if the value to exclude is in the default set.
* The program() source and destination now correctly kill the started child on reload and shutdown.
* The file destination does not use lseek() anymore.
* When setting default template options, all random memory junk is cleared from the object first.
* The order of header include paths was fixed in the test suite, so it should compile cleanly even in the presence of potentially conflicting headers.
Features ========
* The $(format-json) template function, and anything else that may use the same value-pairs command line parser now allow specifying multiple scopes separated by commas (as opposed to having to use the --scope switch multiple times) [#248]
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:
Alexandre Biancalana <biancalana@gmail.com> Balazs Scheidler <bazsi@balabit.hu> Balint Kovacs <blint@balabit.hu> Evan Rempel <erempel@uvic.ca> Fabien Wernli <cpan@faxm0dem.org> Gergely Nagy <algernon@balabit.hu> Lucas McLane <lucas@clicksecurity.com> Marc Falzon <marc.falzon@cloudwatt.com> Michal Privoznik <miso.privoznik@gmail.com> Ryan Frederick Valentijn Sessink <valentijn@sessink.nl>
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/
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
The ChangeLog file is not included with the source package so the rpmbuild process faild when attempting to install the ChangeLog file.
Evan Rempel <erempel@uvic.ca> writes:
The ChangeLog file is not included with the source package so the rpmbuild process faild when attempting to install the ChangeLog file.
Right... I killed the ChangeLog file, because it was useless, but forgot to update the spec file. I will likely remove all packaging stuff from the next release... or well, in 3.5. I'll fix the spec file in 3.4. Thanks for the note! -- |8]
It looks to me that this release does not honour the flush_timeout setting. I have flush_timeout(1000) on my syslog client and my syslog server, but every time I log something on the client, it appears nearly instantly in my "tail -f" output on my server. Can anyone else confirm or refute this? Evan.
We are phasing out flush timeout for a number of reasons, Syslog-ng flushes its output as.soon as no.more messages are available in the queue. On Oct 17, 2013 10:47 PM, "Evan Rempel" <erempel@uvic.ca> wrote:
It looks to me that this release does not honour the flush_timeout setting. I have flush_timeout(1000) on my syslog client and my syslog server, but every time I log something on the client, it appears nearly instantly in my "tail -f" output on my server.
Can anyone else confirm or refute this?
Evan.
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
What I dont know if this was also committed to 3.4 algernon could have a clue. On Oct 17, 2013 10:47 PM, "Evan Rempel" <erempel@uvic.ca> wrote:
It looks to me that this release does not honour the flush_timeout setting. I have flush_timeout(1000) on my syslog client and my syslog server, but every time I log something on the client, it appears nearly instantly in my "tail -f" output on my server.
Can anyone else confirm or refute this?
Evan.
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
participants (5)
-
Balazs Scheidler
-
devel＠balabit.hu
-
Evan Rempel
-
Gergely Nagy
-
Michael Sterrett