| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| | |
... now that we know what we need from a theoretical POV.
|
| | | |
|
| | |
| |
| |
| |
| | |
... plus simplifying free() calls after agreement on mailing list
that we no longer need to check if the pointer is non-NULL
|
| | |
| |
| |
| | |
configuration directives
|
| |\| |
|
| | |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
runtime/queue.c
|
| | | |
| | |
| | |
| | |
| | | |
... badly affecting performance for delayable inputs (but not causeing
any other issues)
|
| | | |\ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- if queues could not be drained before timeout - thanks to
David Lang for pointing this out
- added link to german-language forum to doc set
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... but the action consumer does not do anything really intelligent
with them. But the DA consumer is already done, as is the
main message queue consumer.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... but this code has serious problems when terminating the queue, also
it is far from being optimal. I will commit a series of patches (hopefully)
as I am on the path to the final implementation.
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unfortunatley, I do not have the full list of contributors
available. The patch set was compiled by Ben Taylor, and I made
some further changes to adopt it to the news rsyslog branch. Others
provided much of the base work, but I can not find the names of the
original authors. If you happen to be one of them, please let me
know so that I can give proper credits.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
...to enable users to turn off pthread_yield calls which are
counter-productive on multiprocessor machines (but have been
shown to be useful on uniprocessors)
|
| | | |
| | |
| | |
| | |
| | | |
This occured if queues could not be drained before timeout.
Thanks to David Lang for pointing this out.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This enables us to use more efficient calling conventions and
also helps us keep the on-disk structure of a msg object more
consistent in future releases.
|
| |\| | |
|
| | |\| |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
which so far seems to increase performance. There is also
reason for it to do so, see http://kb.monitorware.com/post14216.html#p14216
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Message parsing is now done as part of main message queue worker
processing (was part of the input thread) This should also improve
performance, as potentially more work is done in parallel.
|
| |/ /
| |
| |
| | |
the critical section what could so with acceptable consequences
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- changed sequence when awakening thread
- removed no longer needed condition variable
- EXPERIMENTALLY added mutex guarding to hostname lookups
this is to be removed if it does not have any verifyable
useful effect
|
| | |
| |
| |
| |
| |
| | |
- removed newly-introduced potential deadlock in debug system
- removed unnecessary pthread_cond_signal
- a bit general cleanup
|
| | |
| |
| |
| |
| |
| |
| | |
There was a wrong order of mutex lock operations. It is hard to
believe that really caused problems, but in theory it could and with
threading we often see that theory becomes practice if something is only
used long enough on a fast enough machine with enough CPUs ;)
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
- added the ability to specify an error log function for the
runtime
- removed dependency of core runtime on dirty.h
Note that it is "better" modularity, not perfect. There is still
work to do, but I think we can for the time being proceed with
other things.
|
| |
|
|
|
| |
cleanup + created an abstract class for global data
items and moved glblGetWorkDir to it
|
| |
|
|
|
| |
reduced dependencies, moved non-runtime files to its own directory except
for some whom's status is unclear
|
| |
|
