diff options
author | Michael Biebl <biebl@debian.org> | 2011-07-11 11:44:16 +0200 |
---|---|---|
committer | Michael Biebl <biebl@debian.org> | 2011-07-11 11:44:16 +0200 |
commit | 6b2af45bc8b2aa4292e3cf92986c01a728ef4d8c (patch) | |
tree | 15c4d4604294a232bf1126f969318ed659b2dc52 /ChangeLog | |
parent | d5294b644649f563f4aa77735ebc6db6ee1776de (diff) | |
download | rsyslog-6b2af45bc8b2aa4292e3cf92986c01a728ef4d8c.tar.gz |
Imported Upstream version 5.8.3upstream/5.8.3
Diffstat (limited to 'ChangeLog')
-rw-r--r-- | ChangeLog | 14 |
1 files changed, 13 insertions, 1 deletions
@@ -1,4 +1,12 @@ --------------------------------------------------------------------------- +Version 5.8.3 [V5-stable] (rgerhards), 2011-07-11 +- systemd support: set stdout/stderr to null - thx to Lennart for the patch +- added support for the ":omusrmsg:" syntax in configuring user messages +- added support for the ":omfile:" syntax in configuring user messages + Note: previous outchannel syntax will generate a warning message. This + may be surprising to some users, but it is quite urgent to alert them + of the new syntax as v6 can no longer support the previous one. +--------------------------------------------------------------------------- Version 5.8.2 [V5-stable] (rgerhards), 2011-06-21 - bugfix: problems in failover action handling closes: http://bugzilla.adiscon.com/show_bug.cgi?id=270 @@ -844,7 +852,11 @@ Version 4.7.0 [v4-devel] (rgerhards), 2010-04-14 Thanks for varmojfekoj for pointing me at this bug. - imported changes from 4.5.6 and below --------------------------------------------------------------------------- -Version 4.6.6 [v4-stable] (rgerhards), 2010-11-?? +Version 4.6.7 [v4-stable] (rgerhards), 2011-07-11 +- added support for the ":omusrmsg:" syntax in configuring user messages +- added support for the ":omfile:" syntax in configuring user messages +--------------------------------------------------------------------------- +Version 4.6.6 [v4-stable] (rgerhards), 2011-06-24 - bugfix: memory leak in imtcp & subsystems under some circumstances This leak is tied to error conditions which lead to incorrect cleanup of some data structures. [backport from v6, limited testing under v4] |