| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
I have now done the necessary cleanup. Looks like everything is in place.
Unfortunately, I do not yet have any actual parser that is not built-in,
but I think we can postpone working on that when the first one appears.
I don't expect troubles in that case, but you never know ;)
|
| |
|
|
|
| |
The implementation is now almost done and works, including doc. I now
need to verify shutdown, guess there are some resource leaks left...
|
| |
|
|
|
|
| |
another milestone commit: the program works, the new interface
is used, some more cleanup is needed and the per-ruleset config
options are still missing. But we are getting closer...
|
| |
|
|
|
|
| |
processing.
THIS IS A VERY IMPORTANT ADDITION, see its doc for why.
|
| |
|
|
|
| |
This offers considerable additional flexibility AND superior performance
(in cases where multiple inputs now can avoid lock contention)
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
also bumped version number and corrected ChangeLog, where I merged
some post 5.3.1 changes into the 5.3.1 section.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
... as well as added multi-ruleset support for imtcp
|
| |
|
|
| |
plus some cleanup...
|
| |
|
|
|
|
| |
... actually, it was not broken, but just very slow. I have now
reduced the number of test messages so that make check will not be
held for an extended period of time.
|
|
|
... this was long overdue, and I finlly tackeld it. It turned out to
be more complex than I initially thought. The next step now probably is
to actually implement multiple rule sets and the beauty that comes
with them.
|
