Changelog

Version 3.21.3 [DEVEL] (rgerhards), 2008-08-13

• added ability to specify flow control mode for imuxsock
• added ability to execute actions only after the n-th call of the action
  This also lead to the addition of two new config directives:
  $ActionExecOnlyEveryNthTime and $ActionExecOnlyEveryNthTimeTimeout
  This feature is useful, for example, for alerting: it permits you to
  send an alert only after at least n occurences of a specific message
  have been seen by rsyslogd. This protectes against false positives
  due to waiting for additional confirmation.

• bugfix: IPv6 addresses could not be specified in forwarding actions
  New syntax @[addr]:port introduced to enable that. Root problem was IPv6
  addresses contain colons.

• somewhat enhanced debugging messages
• imported from 3.18.3:
  • enhanced ommysql to support custom port to connect to server
    Port can be set via new $ActionOmmysqlServerPort config directive
    Note: this was a very minor change and thus deemed appropriate to be
    done in the stable release.

  • bugfix: misspelled config directive, previously was
    $MainMsgQueueWorkeTimeoutrThreadShutdown, is now
    $MainMsgQueueWorkerTimeoutThreadShutdown. Note that the misspelled
    directive is not preserved – if the misspelled directive was used
    (which I consider highly unlikely), the config file must be changed.
    Thanks to lperr for reporting the bug.

Version 3.21.2 [DEVEL] (rgerhards), 2008-08-04

• added $InputUnixListenSocketHostName config directive, which permits to
  override the hostname being used on a local unix socket. This is useful
  for differentiating “hosts” running in several jails. Feature was
  suggested by David Darville, thanks for the suggestion.

• enhanced ommail to support multiple email recipients. This is done by
  specifying $ActionMailTo multiple times. Note that this introduces a
  small incompatibility to previous config file syntax: the recipient
  list is now reset for each action (we honestly believe that will
  not cause any problem – apologies if it does).

• enhanced troubleshooting documentation

Version 3.21.1 [DEVEL] (rgerhards), 2008-07-30

• bugfix: no error was reported if the target of a $IncludeConfig
  could not be accessed.

• added testbed for common config errors
• enhanced config file checking – no active actions are detected
• added -N rsyslogd command line option for a config validation run
  (which does not execute actual syslogd code and does not interfere
  with a running instance)

• somewhat improved emergency configuration. It is now also selected
  if the config contains no active actions

• rsyslogd error messages are now reported to stderr by default. can be
  turned off by the new “$ErrorMessagesToStderr off” directive

Thanks to HKS for suggesting the new features.