- update to 7.2.7 [v7-stable] 2013-04-17
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=134
This commit is contained in:
parent
221a70455a
commit
af393ada32
@ -1,3 +0,0 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8cce8c61610bde4eb09dc379281362650cced4c75097c9756acce8bfaac96bfb
|
||||
size 2704775
|
3
rsyslog-7.2.7.tar.gz
Normal file
3
rsyslog-7.2.7.tar.gz
Normal file
@ -0,0 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4833533a140c1aebed069082ad579ac25e488b647d4d508167dc6e4de75af96d
|
||||
size 2761741
|
@ -1,3 +1,86 @@
|
||||
-------------------------------------------------------------------
|
||||
Fri Apr 19 09:11:23 UTC 2013 - mt@suse.de
|
||||
|
||||
- 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
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=415
|
||||
- bugfix: script == comparison did not work properly on JSON objects
|
||||
[backport from 7.3 branch]
|
||||
- bugfix: imudp scheduling parameters did affect main thread, not imudp
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=409
|
||||
- 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.
|
||||
Thanks to Milan Bartos for the patch.
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=390
|
||||
- bugfix: using group resolution could lead to endless loop
|
||||
Thanks to Tomas Heinrich for the patch.
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=310
|
||||
- bugfix: $mmnormalizeuseramsg paramter was specified with wrong type
|
||||
Thank to Renzhong Zhang for alerting us of the problem.
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=420
|
||||
- bugfix: RainerScript getenv() function caused segfault when var was
|
||||
not found.
|
||||
Thanks to Philippe Muller for the patch.
|
||||
- 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
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=418
|
||||
- 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
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=411
|
||||
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.
|
||||
Thanks to Nathan Stratton Treadway for his great analysis of the
|
||||
problem, which made bug fixing really easy.
|
||||
- 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"
|
||||
Thanks to Joerg Heinemann for alerting us.
|
||||
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=404
|
||||
- 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.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Apr 16 08:49:49 UTC 2013 - mt@suse.de
|
||||
|
||||
|
@ -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.5
|
||||
Version: 7.2.7
|
||||
Release: 0
|
||||
%if 0%{?suse_version} >= 1210
|
||||
%bcond_without systemd
|
||||
|
Loading…
Reference in New Issue
Block a user