| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
runtime/ruleset.c
template.h
threads.c
tools/syslogd.c
|
| | |
| |
| |
| | |
This is done to prevent name claches with libraries.
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
plugins/imfile/imfile.c
plugins/omtesting/omtesting.c
tcpsrv.c
threads.c
|
| | |
| |
| |
| | |
after carful check for copyright holder
|
| | |
| |
| |
| |
| |
| | |
This is considered cosmetic as multiple threads tried to write exactly
the same value into the same memory location without sync. The method
has been changed so this can no longer happen.
|
| | |
| |
| |
| |
| |
| | |
circumstances
This has now been solved, at least for common situations.
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imudp/imudp.c
threads.c
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The original code had quite some issues, which are fixed by this
commit. Also we do more error checking now.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |\ \ \
| |/ /
|/| /
| |/
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/parser.c
runtime/queue.c
runtime/wtp.c
template.c
threads.c
tools/syslogd.c
|
| | | |
|
| | |
| |
| |
| | |
issues
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This was introduced when we re-enabled non-cancel thread termination
a few commits ago. This code has never been released as a tarball,
so that is no bugfix for a release but rather a WiP regression fix
and thus does not need to be mentioned in the ChangeLog.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
...where possible. This provides a more reliable mode of
rsyslogd termination (canceling threads my result in not properly
freed resouces and potential later hangs, even though we perform
proper cancel handling in our code). This is part of an effort to
reduce thread cnacellation as much as possible in rsyslog.
NOTE: some comments indicated that there were problems with some code
that has been re-activated. Testing did not show any issues. My current
assumption is that these issues were related to some other code that
has been removed/changed during the previous restructuring events.
In any case, if there is a shutdown issue, one should carefully look
at this change here!
|
| | |
| |
| |
| |
| |
| | |
a bug showed up during further testing. As this was a side-activity,
I'll probably disable it for the time being and check what's going on
somewhat later (I'll do it tomorrow if I can find it quickly)
|
| |/
|
|
|
|
|
|
| |
... 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).
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/rsyslog_ng_comparison.html
|
| | |
| |
| |
| |
| | |
Thanks to lperr for an excellent bug report that helped detect this
problem.
|
| |/
|
|
|
| |
reduced dependencies, moved non-runtime files to its own directory except
for some whom's status is unclear
|
| | |
|
| |
|
|
|
| |
- changed debug output request signal to SIGUSR2 (as originally intented),
restored SIGUSR1 semantics
|
| |
|
|
|
|
| |
finally in a running state for regular (non disk-assisted) queues, with
a minor nit at shutdown. So I can finally commit the work again to
CVS...
|
| |
|
|
|
| |
- implemented management function for worker thread 0 in order to change
queue workers dynamically -- stage work
|
| |
|
|
|
|
| |
was specified in rsyslog.conf
- fixed a bug that caused a segfault on queues with types other than "disk"
- removed the now longer needed thread TermSyncTool
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
See newsgroup posting for details on the issue:
http://groups.google.com/group/comp.programming.threads/msg/330b9675f17
a1ad6 I tried some mutex operations but came to the conclusion that
this does not really help. So I have now switched to plain thread
cancellation, which so far seems to be OK. Need more practical
experience with other input modules to make a final decision. Thus I
leave all code in and have just disabled the problematic code.
|
| |
|
|
| |
- implemented $klogSymbolsTwice config directive
|
| | |
|
| |
|
|
| |
function
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
