| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... 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)
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is now a "good" rsyslog output module, working as usual. I've also
sorted out some reentrency issues. Code is clean and ready to be tested
in practice ;)
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| / / /
| |/ / / |
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | | |
(double free)
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
runtime/msg.c
I messed up and did some changes during the merge commit ;) But these are
not large, just a little bit of cleanup and some very slight optimizations
inside the msg object.
|
| |\| | |
| | |_|/
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
optimized substring processing, should bring a small enhancement when
forwarding with the default forwarding templates. Also did some uchar
cleanup in msg.c (thus so many changes, in reality they are few...).
|
| | |\|
| | | |
| | | |
| | | |
| | | | |
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.
|
|/ / /
| | |
| | |
| | |
| | | |
This was a result of an internal processing error if maximum field
sizes had been specified in the property replacer.
|
| | |
| | |
| | |
| | |
| | |
| | | |
... first commit in a series of more. Makes worker threads detached. Needs more
testing (will be done soon) and if it works as expected, we can further reduce
code.
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/debug.h
runtime/stream.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
for the stream class and thus finally activating omfile's timeout
capability in a useful way without polling and too-high performance
overhead.
|
| | | |
|
| |\| |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
... 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...
|
| | | |
|
| |\ \ |
|