- Update to 7.2.4 [v7-stable] with following changes:

- enhance: permit RFC3339 timestamp in local log socket messages
    Thanks to Sebastien Ponce for the patch.
  - imklog: added ParseKernelTimestamp parameter (import from 5.10.2)
    Thanks to Marius Tomaschewski for the patch.
  - fix missing functionality: ruleset(){} could not specify ruleset queue
    The "queue.xxx" parameter set was not supported, and legacy ruleset
    config statements did not work (by intention). The fix introduces the
    "queue.xxx" parameter set. It has some regression potential, but only
    for the new functionality. Note that using that interface it is possible
    to specify duplicate queue file names, which will cause trouble. This
    will be solved in v7.3, because there is a too-large regression
    potential for the v7.2 stable branch.
  - imklog: added KeepKernelTimestamp parameter (import from 5.10.2)
    Thanks to Marius Tomaschewski for the patch.
  - bugfix: imklog mistakenly took kernel timestamp subseconds as nanoseconds
    ... actually, they are microseconds. So the fractional part of the 
    timestamp was not properly formatted. (import from 5.10.2)
    Thanks to Marius Tomaschewski for the bug report and the patch idea.
  - bugfix: supportoctetcountedframing parameter did not work in imptcp
  - bugfix: modules not (yet) supporting new conf format were not properly
    registered. This lead to a "module not found" error message instead of
    the to-be-expected "module does not support new style" error message.
    That invalid error message could be quite misleading and actually stop
    people from addressing the real problem (aka "go nuts" ;))
  - bugfix: template "type" parameter is mandatory (but was not)
  - bugfix: some message properties could be garbled due to race condition
    This happened only on very high volume systems, if the same message was
    being processed by two different actions. This was a regression caused
    by the new config processor, which did no longer properly enable msg

OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=120

rsyslog-7.2.3.tar.gz

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

rsyslog-7.2.4.tar.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90af55f696db3209a9ef28d8e8052c48917479dd994838f5ef678b1f701c4540
+size 2702981

rsyslog.changes

@@ -1,3 +1,50 @@
+-------------------------------------------------------------------
+Mon Jan  7 10:58:19 UTC 2013 - mt@suse.com
+
+- Update to 7.2.4 [v7-stable] with following changes:
+  - enhance: permit RFC3339 timestamp in local log socket messages
+    Thanks to Sebastien Ponce for the patch.
+  - imklog: added ParseKernelTimestamp parameter (import from 5.10.2)
+    Thanks to Marius Tomaschewski for the patch.
+  - fix missing functionality: ruleset(){} could not specify ruleset queue
+    The "queue.xxx" parameter set was not supported, and legacy ruleset
+    config statements did not work (by intention). The fix introduces the
+    "queue.xxx" parameter set. It has some regression potential, but only
+    for the new functionality. Note that using that interface it is possible
+    to specify duplicate queue file names, which will cause trouble. This
+    will be solved in v7.3, because there is a too-large regression
+    potential for the v7.2 stable branch.
+  - imklog: added KeepKernelTimestamp parameter (import from 5.10.2)
+    Thanks to Marius Tomaschewski for the patch.
+  - bugfix: imklog mistakenly took kernel timestamp subseconds as nanoseconds
+    ... actually, they are microseconds. So the fractional part of the 
+    timestamp was not properly formatted. (import from 5.10.2)
+    Thanks to Marius Tomaschewski for the bug report and the patch idea.
+  - bugfix: supportoctetcountedframing parameter did not work in imptcp
+  - bugfix: modules not (yet) supporting new conf format were not properly
+    registered. This lead to a "module not found" error message instead of
+    the to-be-expected "module does not support new style" error message.
+    That invalid error message could be quite misleading and actually stop
+    people from addressing the real problem (aka "go nuts" ;))
+  - bugfix: template "type" parameter is mandatory (but was not)
+  - bugfix: some message properties could be garbled due to race condition
+    This happened only on very high volume systems, if the same message was
+    being processed by two different actions. This was a regression caused
+    by the new config processor, which did no longer properly enable msg
+    locking in multithreaded cases. The bugfix is actually a refactoring of
+    the msg locking code - we no longer do unlocked operations, as the use
+    case for it has mostly gone away. It is potentially possible only at
+    very low-end systems, and there the small additional overhead of doing
+    the locking does not really hurt. Instead, the removal of that 
+    capability can actually slightly improve performance in common cases,
+    as the code path is smaller and requires slightly less memory writes.
+    That probably outperforms the extra locking overhead (which in the 
+    low-end case always happens in user space, without need for kernel
+    support as we can always directly aquire the lock - there is no
+    contention at all).
+- Removed imklog-kernel-timestamp-parsing (bnc#783967) patch obsoleted
+  by this version.
+
 -------------------------------------------------------------------
 Fri Nov 23 01:28:46 UTC 2012 - mrueckert@suse.de
 

rsyslog.spec

@@ -1,7 +1,7 @@
 #
 # spec file for package rsyslog
 #
-# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -20,7 +20,7 @@ Name:           rsyslog
 Summary:        The enhanced syslogd for Linux and Unix
 License:        (GPL-3.0+ and Apache-2.0)
 Group:          System/Daemons
-Version:        7.2.3
+Version:        7.2.4
 Release:        0
 %if 0%{?suse_version} >= 1210
 %bcond_without  systemd
@@ -150,7 +150,6 @@ Source2:        rsyslog.conf.in
 Source4:        rsyslog.d.remote.conf.in
 Source5:        rsyslog-service-prepare.in
 Source6:        rsyslog.service.in.in
-Patch1:         0001-imklog-kernel-timestamp-parsing.bnc783967.patch
 
 %description
 Rsyslog is an enhanced multi-threaded syslogd supporting, among others,
@@ -357,7 +356,6 @@ This module provides support to output to an HDFS database.
 
 %endif
 
-
 %if %{with mongodb}
 
 %package module-mongodb
@@ -373,7 +371,6 @@ This module provides support to output to a MongoDB database.
 
 %endif
 
-
 %if %{with hiredis}
 
 %package module-hiredis
@@ -406,7 +403,6 @@ This module provides support for ZeroMQ.
 
 %prep
 %setup -q -n %{name}-%{upstream_version}
-%patch1 -p1
 #
 %if %{with systemd}
 for file in rsyslog-service-prepare rsyslog.service.in ; do