- Update to 6.4.1 [V6-STABLE] 2012-09-06:

- bugfix: multiple main queues with same queue file name were not
    detected.  This lead to queue file corruption. While the root
    cause is a config error, it is a bug that this important and
    hard to find config error was not detected by rsyslog.
  - bugfix: “jsonf” property replacer option did generate invalid
    JSON in JSON, we have “fieldname”:”value”, but the option
    emitted “fieldname”=”value”. Interestingly, this was accepted
    by a couple of sinks, most importantly elasticsearch. Now the
    correct format is emitted, which causes a remote chance that
    some things that relied on the wrong format will break.
    Thanks to Miloslav Trmač for the patch
  - change $!all-json did emit an empty (thus non-JSON) string if
    no libee data was present. It now emits {} and thus valid JSON.
    There is a small risk that this may break some things that
    relied on the previous inconsistency. Thanks to Miloslav Trmač
    for the patch
  - bugfix: omusrsmsg incorrect return state & config warning
    handling. During config file processing, Omusrmsg often
    incorrectly returned a warning status, even when no warning was
    present (caused by uninitialized variable). Also, the core
    handled warning messages incorrectly, and treated them as
    errors. As a result, omusrmsg (most often) could not properly be
    loaded. Note that this only occurs with legacy config action
    syntax. This was a regression caused by an incorrect merge in to
    the 6.3.x codebase.
    Thanks to Stefano Mason for alerting us of this bug.
  - bugfix: Fixed TCP CheckConnection handling in omfwd.c. Interface
    needed to be changed in lower stream classes. Syslog TCP Sending
    is now resumed properly. Unfixed, that lead to non-detection of

OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=93
This commit is contained in:
Marius Tomaschewski 2012-09-17 12:17:44 +00:00 committed by Git OBS Bridge
parent 49f98c6fc5
commit 312b49b6e1
4 changed files with 39 additions and 4 deletions

View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:5962bd9a1194e1acda933820ab33fee0b7fb5425904377ed922c90b2fe8027bc
size 2530470

3
rsyslog-6.4.1.tar.gz Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:6150e81f3338c8624c0e91dbfc83ce753b180993f12a211525a4ac59891efb21
size 2526465

View File

@ -1,3 +1,38 @@
-------------------------------------------------------------------
Mon Sep 17 12:13:04 UTC 2012 - mt@suse.com
- Update to 6.4.1 [V6-STABLE] 2012-09-06:
- bugfix: multiple main queues with same queue file name were not
detected. This lead to queue file corruption. While the root
cause is a config error, it is a bug that this important and
hard to find config error was not detected by rsyslog.
- bugfix: “jsonf” property replacer option did generate invalid
JSON in JSON, we have “fieldname”:”value”, but the option
emitted “fieldname”=”value”. Interestingly, this was accepted
by a couple of sinks, most importantly elasticsearch. Now the
correct format is emitted, which causes a remote chance that
some things that relied on the wrong format will break.
Thanks to Miloslav Trmač for the patch
- change $!all-json did emit an empty (thus non-JSON) string if
no libee data was present. It now emits {} and thus valid JSON.
There is a small risk that this may break some things that
relied on the previous inconsistency. Thanks to Miloslav Trmač
for the patch
- bugfix: omusrsmsg incorrect return state & config warning
handling. During config file processing, Omusrmsg often
incorrectly returned a warning status, even when no warning was
present (caused by uninitialized variable). Also, the core
handled warning messages incorrectly, and treated them as
errors. As a result, omusrmsg (most often) could not properly be
loaded. Note that this only occurs with legacy config action
syntax. This was a regression caused by an incorrect merge in to
the 6.3.x codebase.
Thanks to Stefano Mason for alerting us of this bug.
- bugfix: Fixed TCP CheckConnection handling in omfwd.c. Interface
needed to be changed in lower stream classes. Syslog TCP Sending
is now resumed properly. Unfixed, that lead to non-detection of
downstate of remote hosts.
------------------------------------------------------------------- -------------------------------------------------------------------
Tue Sep 4 18:32:29 UTC 2012 - andreas.stieger@gmx.de Tue Sep 4 18:32:29 UTC 2012 - andreas.stieger@gmx.de

View File

@ -20,7 +20,7 @@ Name: rsyslog
Summary: The enhanced syslogd for Linux and Unix Summary: The enhanced syslogd for Linux and Unix
License: (GPL-3.0+ and Apache-2.0) License: (GPL-3.0+ and Apache-2.0)
Group: System/Daemons Group: System/Daemons
Version: 6.4.0 Version: 6.4.1
Release: 0 Release: 0
# for setting those bcond_with* configs see # for setting those bcond_with* configs see
# http://lizards.opensuse.org/2008/09/12/conditional-features-aka-use-flags/ # http://lizards.opensuse.org/2008/09/12/conditional-features-aka-use-flags/