Hello community,
here is the log from the commit of package patchinfo.1640 for
openSUSE:12.3:Update checked in at 2013-05-06 13:14:23
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:12.3:Update/patchinfo.1640 (Old)
and /work/SRC/openSUSE:12.3:Update/.patchinfo.1640.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "patchinfo.1640"
Changes:
--------
New Changes file:
NO CHANGES FILE!!!
New:
----
_patchinfo
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ _patchinfo ++++++
<patchinfo>
<packager>mtomaschewski</packager>
<category>recommended</category>
<rating>low</rating>
<summary>rsyslog, libestr, liblognorm: Several fixes</summary>
<description>This update fixes the following issues for rsyslog, libestr and
liblognorm:
- rsyslog:
+ bnc#809852: update to 7.2.7 [v7-stable] 2013-04-17:
* rsyslogd startup information is now properly conveyed back to init when
privileges are beging dropped. Actually, we have moved termination of the
parent in front of the priv drop. So it shall work now in all cases. See code
comments in commit for more details.
* If forking, the parent now waits for a maximum of 60 seconds for
termination by the child
* Improved debugging support in forked (auto-backgrounding) mode. The
rsyslog debug log file is now continued to be written across the fork.
* updated systemd files to match current systemd source
* bugfix: failover/action suspend did not work correctly. This was
experienced if the retry action took more than one second to complete. For
suspending, a cached timestamp was used, and if the retry took longer, that
timestamp was already in the past. As a result, the action never was kept in
suspended state, and as such no failover happened. The suspend functionalit now
does no longer use the cached timestamp (should not have any performance
implication, as action suspend occurs very infrequently).
* bugfix: nested if/prifilt conditions did not work properly
* bugfix: script == comparison did not work properly on JSON objects
* bugfix: imudp scheduling parameters did affect main thread, not imudp
* bugfix: imuxsock rate-limiting could not be configured via legacy conf.
Rate-limiting for the system socket could not be configured via legacy
configuration directives. However, the new-style RainerScript config options
worked.
* bugfix: using group resolution could lead to endless loop
* bugfix: $mmnormalizeuseramsg paramter was specified with wrong type
* bugfix: RainerScript getenv() function caused segfault when var was not
found.
* bugfix: several issues in imkmsg (see bug tracker:
http://bugzilla.adiscon.com/show_bug.cgi?id=421#c8)
* bugfix: imuxsock was missing SysSock.ParseTrusted module parameter. To
use that functionality, legacy rsyslog.conf syntax had to be used. Also, the
doc was missing information on the "ParseTrusted" set of config directives.
* bugfix: parameter action.execOnlyWhenPreviousIsSuspended was accidently
of integer-type. For obvious reasons, it needs to be boolean. Note that this
change can break existing configurations if they circumvented the problem by
using 0/1 values.
* doc bugfix: rsyslog.conf man page had invalid file format info
+ update to 7.2.6 [v7-stable] 2013-03-05:
* slightly improved config parser error messages when invalid escapes happen
* bugfix: include files got included in the wrong order. This happens if an
$IncludeConfig directive was done on multiple files (e.g. the distro default of
$IncludeConfig /etc/rsyslog.d/*.conf). In that case, the order of include file
processing is reversed, which could lead to all sorts of problems.
* bugfix: omelasticsearch failed when authentication data was provided ...
at least in most cases it emitted an error message: "snprintf failed when
trying to build auth string"
* bugfix: some property-based filter were incorrectly parsed. This usually
lead to a syntax error on startup and rsyslogd not actually starting up. The
problem was the regex, which did not care for double quote characters to follow
in the action part - unfortunately something that can frequently happen with
v6+ format. An example:
| :programname, isequal, "as" {action(type="omfile" ...) }
| Here, the part
| :programname, isequal, "as" {action(type="omfile"
| was treated as the property filter, and the rest as action part.
Obviously, this did not work out. Unfortunately, such situations usually
resulted in very hard to understand error messages.
+ Removed rsyslog.conf from doc file list, not shipped any more.
+ bnc#812447: restore SELinux label when creating xconsole
- liblognorm:
+ bnc#809852: Update to 0.3.6:
* bugfix: unitialized variable could lead to rulebase load error
- liberf:
+ bnc#809852: Update to 0.1.5:
* bugfix: es_strncmp() did not work correctly</description>
<issue tracker="bnc" id="809852">rsyslog: message from the cron daemon go to
the wrong logfile</issue>
<issue tracker="bnc" id="812447">Incorrect SELinux label for
/dev/xconsole</issue>
</patchinfo>
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
