[syslog-ng-announce] syslog-ng Premium Edition 3.2.1 has been released

[devel at balabit.hu]

------------------------------------------------------------------------------
PACKAGE             : syslog-ng Premium Edition
VERSION             : 3.2.1
SUMMARY             : new feature release
DATE                : Oct 26, 2010
------------------------------------------------------------------------------

DESCRIPTION:

  syslog-ng Premium Edition version 3.2.1 is the first maintenance release of
  the 3.2 feature release branch. 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 3.2 Administrator Guide.

  WARNING:
  Downgrading from a feature release to an earlier (and thus unsupported)
  feature release, or to the stable release is not supported.
  This means that once you upgrade a system from a stable release (e.g., 3.0)
  to a feature release (e.g., 3.1), you will have to keep upgrading to the new
  feature releases until the next stable version release (e.g., 4.0) is
  published, or risk using an unsupported product.

Bugfixes:

        Installers
        .RUN installer:
        * If the /var/log directory did not exist while installing syslog-ng,
          the installer did not create it, so the logs of the installation
          were not available. This has been corrected.

        RPM installer:
        * The rcd scripts were missing from the SUSE10 installer.
          This has been corrected.

        DEB installer:
        * During upgrades, the installer did not migrate the license.txt
          file. This has been corrected.

        Core
        * On Solaris 10 platforms, if syslog-ng PE was running and there was no
          PID file or the PID file contained an incorrect PID number, syslog-ng
          switched to maintenance mode when receiving a STOP signal.
          This has been corrected.
        * The syslog-ng PE application terminated if it received a message with
          a facility number above 23. This has been corrected.
        * In certain cases, reloading a configuration that used the sql()
          driver caused the
          syslog-ng PE application to terminate. This has been corrected.
        * When using the IETF-syslog protocol, the sequenceID part of SDATA was
          missing from local messages. This has been corrected.

        File handling
        * In certain very rare cases, syslog-ng PE created corrupted logstore
          files. This has been corrected.
        * In certain cases when using many wildcard file sources, the syslog-ng
          PE application used a lot of CPU. This has been corrected. Only UNIX
          platforms were affected.
        * When accessing files from an NFS-mounted volume, the syslog-ng PE
          application could go into an infinite loop when the source files
          were deleted from NFS. This has been corrected.
        * The lgstool did not handle properly if its parameters were specified
          in an unexpected order. This has been corrected.

        Configuration
        * The statistics were not correctly updated after reloading the
          configuration of syslog-ng PE. This has been corrected.
        * The syslog-ng PE application calculated the checksum only for the
          main configuration file, and not for included files. This has been
          corrected.
        * The $HOST macro displayed incorrect values if the chained_hostnames()
          and normalize_hostnames() options were used together.
          This has been corrected.
        * Two new macros are available, referring to the date of the log
          messages: $MSEC (millisecond) and $USEC (microsecond).

        Multiple lines
        * The syslog-ng PE application terminated when the
          multiple-line-prefix() option was used and the source file was
          overwritten or rotated. This has been corrected.
        * When using the multiple-line-prefix() option without the
          multi-line-garbage() option, the syslog-ng PE application will wait
          only 10 seconds for the next message. If no new message arrives, the
          last message is assumed to be complete and sent to the destination.

        Accented characters
        * The pdbtool application did not accept accented characters.
          This has been corrected.
        * Pattern matching did not properly handle patterns containing accented
          characters. This has been corrected.

        Other
        * The loggen application did not correctly parse messages read from
          file sources. This has been corrected.

DOWNLOAD:

  Download the latest binaries from:

  http://www.balabit.com/network-security/syslog-ng/central-syslog-server/upgrades/

  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 3.2.1 Administrator Guide at:
  http://www.balabit.com/support/documentation/





-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 199 bytes
Desc: not available
Url : http://lists.balabit.hu/pipermail/syslog-ng-announce/attachments/20101109/4ed0d0f5/attachment.pgp