| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
... but an alternate approach via pthread_kill. This is somewhat safer as we
do not need to think about the cancel-safeness of all libraries we use.
However, not all inputs can easily supported, so this now is a feature
that can be requested by the input module (the most important ones
request it).
|
| |
|
|
|
|
|
| |
... but this sets stage for potential future optimizations, especially
the capability to use multiple reception threads.
|
|
|
|
|
|
| |
the new handling will hopefully spare a few cycles, as function calls
(and most importantly parameter generation!) or now only done when
debug messages are actually active.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
code review brought up some few places where we may have run into a race.
They have most probably been introduced during the recent set of changes. But
I do not look at older versions because of the changed architecture, one can
not simply backport this patch.
|
|
|
|
|
| |
This did NOT leak based on message volume. Also, did some cleanup during
the commit.
|
|
|
|
|
| |
... greater performance and was able to remove a potential troublespot
in a cancel cleanup handler.
|
|
|
|
|
|
| |
...if not running in direct mode. Previous versions could run without
any active workers. This simplifies the code at a very small expense.
See v5 compatibility note document for more in-depth discussion.
|
| |
|
|
|
|
| |
... as well as some cleanup
|
| |
|
|
|
|
|
| |
... by utilizing that we need to modify a state variable only in
a sequential way during shutdown.
|
|
|
|
|
|
|
|
|
| |
... could even remove one mutex by using a better algorithm. I think I also
spotted some situation in which a hang could have happened. As I can't fix it
in v4 and less without moving to the new engine, I make no effort in testing
this out. Hangs occur during shutdown, only (if at all). The code changes
should also result in some mild performance improvement. Some bug potential,
but overall the bug potential should have been greatly reduced.
|
|
|
|
| |
reducing the number of thread cancellation state changes
|
|\
| |
| |
| |
| |
| | |
Conflicts:
runtime/wti.c
runtime/wtp.c
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
This is for another prctl() call, not present in the beta version (looks like it
would make sense to stick these into a utility function)
|
| | |\ |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
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:
ChangeLog
|
| |\ \ \ \
| | | |/ /
| | |/| | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
v4-beta was so far unreleased, so it was a bug only here
|
| | |\ \ \
| | | | |/
| | | |/| |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... only those things that were obvious (and puzzled people looking at
the code without konwing the subtle issues of HUP ;)).
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... but the rest of the code is not yet cleaned-up. Will do that
slowly over time... (huge potential, but must be done carefully)
|
| | | | |
| | | | |
| | | | |
| | | | | |
... was not well maintained at all, now refering to git
|
| | | | | |
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |/ / / |
|
| | | | |
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We are doing this to support removal of restart-type HUP in v5.
Elaborate doc added to explain reasoning and actions to be taken.
|
| | | |
| | | |
| | | |
| | | | |
html doc is better
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
... part of the deprecation effort for v5
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...after sending n messages (actually, it re-opens the connection, the
name is used because this is a concept very similiar to
$ActionUDPRebindInterval). New config directive $ActionSendTCPRebindInterval
added for the purpose. By default, rebinding is disabled. This is considered#
useful for load balancers.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
added tcp output rebinding option.
needs some more testing and doc
|
| | | | |
| | | | |
| | | | |
| | | | | |
needs some more testing and doc
|
|\| | | | |
|
| |\| | | |
|
| | | | | |
|