| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| |
| |
| | |
in which debug output can be generated only after the process has started,
but not right from the beginning. This is assumed to be useful for
hard-to-find bugs. Also improved the doc on the debug system.
|
|\ \ |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | |
| | |
| | |
| | | |
this was a regression from the omfile rewrite in 4.5.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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...
|
| | |
| | |
| | |
| | |
| | | |
looks like we are almost done and need only to add the ruleset parser-specific
config options.
|
| | |
| | |
| | |
| | |
| | |
| | | |
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...
|
| | |
| | |
| | |
| | | |
... getting the module structure a bit cleaner ;)
|
| | |
| | |
| | |
| | |
| | | |
This is a milestone commit, which adds new code that breaks
nothing, but also does not add any visible change. Just prep work...
|
| | |
| | |
| | |
| | |
| | |
| | | |
I cleaned up a lot of config variable access along the way. This
version compiles and runs, but does not yet offer any enhanced
functionality. pmrfc5424 is just a dummy that is not yet being used.
|
| | |
| | |
| | |
| | |
| | |
| | | |
now cleaner and hopefully usuable as a basis for loadable parser
modules. I also cleaned up/consolidated some of the internal
message generation functionality in rsyslogd.
|
|\| | |
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imrelp/imrelp.c
|
| | |\ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
improperly handled.
This was a regression of one of the last bugfixes, so no previously released
version contained this bug (thus it does not show up in the ChangeLog).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problems could happen if the queue worker needed to be cancelled
and this cancellation happened inside queue-code (including
wtp, wti). We have now solved this by disabling cancellation while
in this code and only enabling it when working inside the user consumer.
This exactly matches the use case for which cancellation may be needed.
|
| | | |
| | | |
| | | |
| | | | |
... but in anticipation of changing cancel processing altogether...
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
these occured in very unusual scenarios where we had a DA-queue running
in parallel and very lengthy actions. Then, in some situations, the
shutdown could hang. The code needs some addition lab time, but
is believed to be much better than any previous version.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
primarily a problem of imdiag. Also added some fix for a potential
situation during cancel processing. That one is not considered vital
and may later be removed again.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We do now enqueue those objects that are left unprocessed. This enables
us to delete the full batch, what is exactly what we need to do.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... but this brings a lot of problems with it. The issue is that
we still have a sequential store and we do not know how we could
delete the one entry right in the middle of processing. I keep this
branch if we intend to move on with it - but for now I look into a
different solution...
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
support for enhancing probability of memory addressing failure by
using non-NULL default value for malloced memory (optional, only if
requested by configure option). This helps to track down some
otherwise undetected issues within the testbench and is expected
to be very useful in the future.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
runtime/queue.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
simplified and thus speeded up the queue engine, also fixed some
potential race conditions (in very unusual shutdown conditions)
along the way. The threading model has seriously changes, so there may
be some regressions.
NOTE: the code passed basic tests, but there is still more work
and testing to be done. This commit should be treated with care.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
... non-working version!
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Failed for both pure disk as well as DA queues. Now, we emit an error
message and disable disk queueing facility.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
this was a regression of the recent imudp multi-ruleset enhancement
bug was not in any released version
|
|\ \ \ \ \ \ |
|
| | |/ / / /
| |/| | | | |
|
|/ / / / / |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
runtime/msg.c
|
| | | | |
| | | | |
| | | | |
| | | | | |
This was a recently introduced regression.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
bugfix: debug string larger than 1K were improperly displayed. Max size
is now 32K, and if a string is even longer it is meaningful truncated.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
also bumped version number and corrected ChangeLog, where I merged
some post 5.3.1 changes into the 5.3.1 section.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
This was a recently introduced regression.
|