Changelog for 5.7.3 (v5-beta)

Version 5.7.3 [V5-BETA] (rgerhards), 2011-02-07

  • added support for processing multi-line messages in imfile
    thanks to David Lang for implementing this
  • added $IMUDPSchedulingPolicy and $IMUDPSchedulingPriority config settings
  • added $LocalHostName config directive
  • bugfix: fixed build problems on some platforms
    namely those that have 32bit atomic operations but not 64 bit ones
  • bugfix: local hostname was pulled too-early, so that some config
    directives (namely FQDN settings) did not have any effect
  • bugfix: imfile did duplicate messages under some circumstances
  • added $OMMySQLConfigFile config directive
  • added $OMMySQLConfigSection config directive

Changelog for 6.1.3 (v6-devel)

Version 6.1.3 [DEVEL] (rgerhards), 2011-02-01

  • experimental support for monogodb added
  • added $IMUDPSchedulingPolicy and $IMUDPSchedulingPriority config settings
  • added $LocalHostName config directive
  • improved tcpsrv performance by enabling multiple-entry epoll
    so far, we always pulled a single event from the epoll interface.
    Now 128, what should result in performance improvement (less API
    calls) on busy systems. Most importantly affects imtcp.

  • imptcp now supports non-cancel termination mode, a plus in stability
  • imptcp speedup: multiple worker threads can now be used to read data
  • new directive $InputIMPTcpHelperThreads added
  • bugfix: fixed build problems on some platforms
    namely those that have 32bit atomic operations but not 64 bit ones

  • bugfix: local hostname was pulled too-early, so that some config
    directives (namely FQDN settings) did not have any effect

  • enhanced tcpflood to support multiple sender threads
    this is required for some high-throughput scenarios (and necessary to
    run some performance tests, because otherwise the sender is too slow).

  • added some new custom parsers (snare, aix, some Cisco “specialities”)
    thanks to David Lang

Changelog for 5.6.3 (v5-stable)

Version 5.6.3  [V5-STABLE] (rgerhards), 2011-01-26

  • bugfix: action processor released memory too early, resulting inpotential issue in retry cases (but very unlikely due to anotherbug, which I also fixed — only after the fix this problem here became actually visible).
  • bugfix: batch processing flagged invalid message as “bad” under somecircumstances
  • bugfix: unitialized variable could cause issues under extreme conditionsplus some minor nits. This was found after a clang static code analyzeranalysis (great tool, and special thanks to Marcin for telling me about it!)
  • bugfix: batches which had actions in error were not properly retried inall cases
  • bugfix: imfile did duplicate messages under some circumstances
Scroll to top