Modular Syslog

File Release Notes and Changelog

Release Name: v1.09preview

Notes: <div><p>This release is not yet production ready. Before I would be comfortable, we should have a regression test suite that provides a set of tests that touches each module. I have already started and encourage any user who has a test to send them to the users mailing list.</p></div>

---

Changes: <div> <p>This release incorporates many changes and should not yet be considered production ready. Many outstanding bugs have been fixed and several new modules have been added. </p> <div> New/Enhanced Modules: <ul> <li>The om_regex module now handles substitution; note however, that time and date matching have been removed. A new module is in the works to handle time and date matching/munging. </li> <li>A directory module can be used to write out messages into individual files. The intent is to use the directory as queue to be processed by some daemon. Each time the module has created such a file it sets a semaphore. </li> <li>The im_file module has been rewritten and should work as expected now. Note; it does not notice new records in the file immediately as do the other input modules. Rather it checks the file within 5 seconds. This module is very useful in testing. </li> <li>An im_serial module is in the works for munging arbitrary messages from serial sources into syslog format. </li> <li>There is a refraction input module (refraction meaning, to actively prevnet the rule from firing). There have been several requests for the functions this module provides. im_refract takes two options one which prevents the rule from firing if the rule has previously fired within the specified period. The other prevents firing if a preceeding rule has fired on the current message. </li> <li>Test cases are being introduced. The current tests are directed toward output modules. Input modules are a little trickier to test and some changes will be needed in the source to make msyslog more testable. </li> </ul> </div> </div>