| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
... getting the module structure a bit cleaner ;)
|
|\ |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
runtime/msg.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
This resulted in build errors if no Java was present on the build system,
even though none of the selected option actually required Java.
(I forgot to backport a similar fix to newer releases).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
processing.
THIS IS A VERY IMPORTANT ADDITION, see its doc for why.
|
| | |
| | |
| | |
| | |
| | | |
thus some unpredictable behavior and a false negative test result
could occur.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
actually, the runtime dummy was missing some global entities, these
have now been added.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | | |
- added a test to check handling of damaged .qi files on startup
- made sure each test identifies itself on startup
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
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:
tools/syslogd.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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!
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We are "abusing" the parser tests to test the TCP/UDP reception
handling. Thus we do not run the other tests through to an IPv4
only config. It acutally is not that parser that matters but rather
the hope to find some init issues when running with only a single
listening socket (in IPv6, we usually both have an IPv4 AND an IPv6
listening socket, what - as practice has shown - may hide listener
setup errors).
|
| | | | | |
|
| |/ / /
|/| | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- bugfix: solved potential (temporary) stall of messages when the queue was
almost empty and few new data added (caused testbench to sometimes hang!)
- fixed some race condition in testbench
- added more elaborate diagnostics to parts of the testbench
- solved a potential race inside the queue engine
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
made shutdown more reliable by makeing sure that the main queue DA worker
is only cancelled if this is actually unavoidable. Also moved down the
deletion of rsyslogd's pid file to immediately before termination, so
that absence of the file is a proper indication that rsyslogd has
finished (in the past, e.g. the testbench accidently ran two intances
as the pid file was deleted too early). Also some improvments to the
testbench, namely to handle aborts more intelligently (but still not
perfect).
|
| | | |
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | | |
Some devices seem to create them and I do not see any harm in supporting that.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
... as well as some cleanup
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/nettester.c
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
based on now working with detached threads. This is probably the biggest
patch in this series and with large bug potential.
|
|\ \ \ \
| |/ / /
|/| / /
| |/ / |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/nettester.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was a result of an internal processing error if maximum field
sizes had been specified in the property replacer.
Also did some testbench improvements, including omstdout.
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/debug.h
runtime/stream.c
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... this is necessary in preparation for the final solution (we need
to have a "unified" writer). If it causes worse performance to have the
zip writher togehter with the synchronous write, we may do an async write...
|
| |/ /
| | |
| | |
| | |
| | | |
... seems to work on quick testing, but needs a far more testing
and improvement. Good milestone commit.
|
| | | |
|