8.1.6

Version 8.1.6 [devel] 2014-02-20

• omfile: permit to set global defaults for action parameters
  Thanks to Nathan Brown for the patch.
  See also: https://github.com/rsyslog/rsyslog/pull/23
• add capability to escape control characters in the C way of doing it
  adds new global parameter “parser.escapeControlCharactersCStyle”
  Thanks to Nathan Brown for the patch.
  See also: https://github.com/rsyslog/rsyslog/pull/13
• parser global parameters can now be set using RainerScript global()
  Thanks to Nathan Brown for the patch.
  See also: https://github.com/rsyslog/rsyslog/pull/23
• omprog: guard program-to-be-executed against CTL-C
  This can frequently happen in debug mode, where rsyslog is terminated
  by ctl-c. In any case, SIGINT is not meant to control the child process,
  so it should be blocked.
• omprog bugfix: parameter “forceSingleInstance” is NOT mandatory
• add new jsonr property replacer option
  Thanks to Nathan Brown for the patch.
• added external plugin interface
• ommongodb: add authentication support (untested)
  Thanks to JT for the patch.
  See also: https://github.com/rsyslog/rsyslog/pull/17
• bugfix: json templates are improperly created
  Strings miss the terminating NUL character, which obviously can lead
  to all sorts of problems.
  See also: https://github.com/rsyslog/rsyslog/issues/27
  Thanks to Alain for the analysis and the patch.
• ompgsql bugfix: improper handling of auto-backgrounding mode
  If rsyslog was set to auto-background itself (default code behaviour, but
  many distros now turn it off for good reason), ompgsql could not
  properly connect. This could even lead to a segfault. The core reason
  was that a PG session handle was kept open over a fork, something that
  is explicitely forbidden in the PG API.
  Thanks to Alain for the analysis and the patch.
• bugfix: ommongodb’s template parameter was mandatory but should have
  been optional
  Thanks to Alain for the analysis and the patch.
• bugfix: end of batch processing was not 100% correct. Could lead to
  outputs not properly wirting messages. At least omelasticsearch did not
  write anything to the database due to this bug.
  See: https://github.com/rsyslog/rsyslog/issues/10
  Thanks to Radu Gheorghe for reporting the issue.