diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2012-11-20 10:15:36 +0100 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2012-11-20 10:15:36 +0100 |
commit | 9c25e344f2734c7f82fdad43c2fd88e91b27c315 (patch) | |
tree | 535cbbc3c5acf40e000b31302594077fc3f8444f | |
parent | 1d3c4454403eb038220f8fd075f0bc836b2e03ed (diff) | |
download | rsyslog-9c25e344f2734c7f82fdad43c2fd88e91b27c315.tar.gz rsyslog-9c25e344f2734c7f82fdad43c2fd88e91b27c315.tar.bz2 rsyslog-9c25e344f2734c7f82fdad43c2fd88e91b27c315.zip |
document fixed regression
-rw-r--r-- | ChangeLog | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -1,4 +1,16 @@ ---------------------------------------------------------------------------- +Version 7.2.3 [v7-stable] 2012-10-?? +- regression fix: rsyslogd terminated when wild-card $IncludeConfig did not + find actual include files. For example, if this directive is present: + $IncludeConfig /etc/rsyslog.d/*.conf + and there are no *.conf files in /etc/rsyslog.d (but rsyslog.d exists), + rsyslogd will emit an error message and terminate. Previous (and expected) + behaviour is that an empty file set is no problem. HOWEVER, if the + directory itself does not exist, this is flagged as an error and will + load to termination (no startup). + Unfortunately, this is often the case by default in many distros, so this + actually prevents rsyslog startup. +---------------------------------------------------------------------------- Version 7.2.2 [v7-stable] 2012-10-16 - doc improvements - enabled to build without libuuid, at loss of uuid functionality |