Changelog

Version 5.3.3 [DEVEL] (rgerhards), 2009-10-27

• simplified and thus speeded up the queue engine, also fixed some potential race conditions (in very unusual shutdown conditions) along the way. The threading model has seriously changes, so there may be some regressions.
• enhanced test environment (inlcuding testbench): support for enhancing probability of memory addressing failure by using non-NULL default value for malloced memory (optional, only if requested by configure option). This helps to track down some otherwise undetected issues within the testbench.
• bugfix: potential abort if inputname property was not set primarily a problem of imdiag
• bugfix: message processing states were not set correctly in all cases however, this had no negative effect, as the message processing state was not evaluated when a batch was deleted, and that was the only case where the state could be wrong.
  

Version 5.3.2 [DEVEL] (rgerhards), 2009-10-21

• enhanced omfile to support transactional interface. This will increase performance in many cases.
• added multi-ruleset support to imudp
• re-enabled input thread termination handling that does avoid thread cancellation where possible. This provides a more reliable mode of rsyslogd termination (canceling threads my result in not properly freed resouces and potential later hangs, even though we perform proper cancel handling in our code). This is part of an effort to reduce thread cancellation as much as possible in rsyslog.
  NOTE: the code previously written code for this functionality had a subtle race condition. The new code solves that.

• enhanced immark to support non-cancel input module termination
• improved imudp so that epoll can be used in more environments, fixed potential compile time problem if EPOLL_CLOEXEC is not available.
• some cleanup/slight improvement:
  • changed imuxsock to no longer use deprecated submitAndParseMsg() IF
  • changed submitAndParseMsg() interface to be a wrapper around the new way of message creation/submission. This enables older plugins to be used together with the new interface. The removal also enables us to drop a lot of duplicate code, reducing complexity and increasing maintainability.
• bugfix: segfault when starting up with an invalid .qi file for a disk queue
  Failed for both pure disk as well as DA queues. Now, we emit an error message and disable disk queueing facility.

• bugfix: potential segfault on messages with empty MSG part. This was a recently introduced regression.
• bugfix: debug string larger than 1K were improperly displayed. Max size is now 32K, and if a string is even longer it is meaningfully truncated.
  

Version 5.3.0 [DEVEL] (rgerhards), 2009-09-14

• begun to add simple GUI programs to gain insight into running rsyslogd instances and help setup and troubleshooting (active via the –enable-gui ./configure switch)
• changed imudp to utilize epoll(), where available. This shall provide slightly better performance (just slightly because we called select() rather infrequently on a busy system)
• added new config option $ActionWriteAllMarkMessages this option permites to process mark messages under all circumstances, even if an action was recently called. This can be useful to use mark messages as a kind of heartbeat.
• added new config option $InputUnixListenSocketCreatePath to permit the auto-creation of pathes to additional log sockets. This turns out to be useful if they reside on temporary file systems and rsyslogd starts up before the daemons that create these sockets (rsyslogd always creates the socket itself if it does not exist).
• added $LogRSyslogStatusMessages configuration directive permitting to turn off rsyslog start/stop/HUP messages. See Debian ticket http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463793
• bugfix: hostnames with dashes in them were incorrectly treated as malformed, thus causing them to be treated as TAG (this was a regression introduced from the “rfc3164 strict” change in 4.5.0). Testbench has been updated to include a smaple message with a hostname containing a dash.
• bugfix: strings improperly reused, resulting in some message properties be populated with strings from previous messages. This was caused by an improper predicate check.
• added new config directive $omfileForceChown [import from 4.7.0]
  

Version 5.3.1 [DEVEL] (rgerhards), 2009-09-05

• added $AbortOnUncleanConfig directive – permits to prevent startup when there are problems with the configuration file. See it’s doc for details.
• included some important fixes from v4-stable:
  • bugfix: invalid handling of zero-sized messages
  • bugfix: zero-sized UDP messages are no longer processed
  • bugfix: random data could be appended to message
  • bugfix: reverse lookup reduction logic in imudp do DNS queries too often
• bugfixes imported from 4.5.4:
  • bugfix: potential segfault in stream writer on destruction
  • bugfix: potential race in object loader (obj.c) during use/release
  • bugfixes: potential problems in out file zip writer