------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 4 LTS (4.0.5) SUMMARY : new stable release DATE : Mar 9, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Premium Edition (4 LTS (4.0.5)) has been released. For a full description on stable and feature releases, see Section 2.16. Stable and feature releases of syslog-ng PE in The syslog-ng Premium Edition 4 LTS (4.0.5) Administrator Guide. CHANGES: 4 LTS (4.0.5) Fri, 09 Mar 2012 13:26:48 +0100 Fixed issues: #25577: Fixed a syslog-ng deadlock in case of failed SQL transactions #24425: In rare cases, syslog-ng crashes on Solaris #24546: Memory leak when reading from disk buffer #24210: The lgstool tail command fails with an error message #22763: The trusted-keys() option is ignored if the value was not an SHA1 key #23297: SQL: messages lost from FIFO when reloading syslog-ng #23308: SQL: When shutting down syslog-ng, messages from FIFO are lost #23110: Debug logs of syslog-ng include every modification of the log messages #23176: syslog-ng removes the PRI value if it is 0 #23409: Reading from files using the wildcard file source is slow #25963: syslog-ng does not start if the persist file is invalid #23114: A single log message is not sent using TLS, two messages are required #23418: Losing messages when flow-control is enabled #23555: syslog-ng crashes when the pad_size() is longer than the message #22636: The unix-stream and dgram drivers duplicate messages in some cases #25956: syslog-ng stops processing messages when the timestamping server is slow #25978: Receiving messages from obsolete network sources causes a segfault #25979: Rewrite: Attempting to rewrite a read-only field overwrites the MESSAGE field #25995: When reloading the configuration is not successful, syslog-ng can duplicate log messages #22693: In some cases the disk buffer file becomes unreadable #24580: If the flush_timeout() is low, the throttle option is not working for file destinations CHANGES: Deadlock detection: * The supervisor process of syslog-ng can automatically check if syslog-ng entered a deadlock and does not respond. If the syslog-ng process does not respond, the supervisor process restarts syslog-ng. By default, the supervisor process checks for timeouts every 300 seconds. To modify this value, use the '--deadlock-check-timeout' or '-D' command-line option of syslog-ng For details on the fixed issues see our new issue tracking page at https://www.balabit.com/mybalabit/fixed_bugs/revision/ The documentation of syslog-ng 4 LTS, including the installation and user guides is available in PDF, HTML, and single-page HTML format at: http://www.balabit.com/support/documentation/ UPGRADE: For details on upgrading and possible upgrade paths, read Section 3.5., Upgrading syslog-ng in the The syslog-ng Premium Edition 4 LTS Administrator Guide: http://www.balabit.com/support/documentation/syslog-ng-pe-v4.0-guide-admin-e... Kind Regards, BalaBit IT Security DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/upgr... Note that to download the binaries, you have to login into your MyBalaBit account. The documentation of the syslog-ng application is available in The syslog-ng Premium Edition 4 LTS (4.0.5) Administrator Guide at: http://www.balabit.com/support/documentation/