| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Thanks to Miloslav Trmač for providing patches and suggestions
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=330
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\| |
|
| |\ |
|
|\ \ \ |
|
| | | | |
|
| |\ \ \
| | | |/
| | |/|
| | | |
| | | | |
Conflicts:
runtime/queue.c
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a minor optimization to spare some cycles if the timeout
is set to immediate discard
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
even if there was a disk queue associated with it. The root cause of this
problem was that it makes no sense to delay messages once they arrive in the
action queue - the "input" that is being held in that case is the main
queue worker, what makes no sense.
Thanks to Marcin for alerting us on this problem and providing
instructions to reproduce it.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will mark them as SKIPPED instead of FAILED, making it at least
in theory possible to get 0 FAILED tests even when running as an
unprivileged user.
|
| | | |
| | | |
| | | |
| | | | |
Valgrind tests depend on imdiag as well.
|
| | | | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
if rsyslog was set to auto-background (thus fork, the default) and debug
mode to stdout was enabled, debug messages ended up in the first log file
opened. Currently, stdout logging is completely disabled in forking mode
(but writing to the debug log file is still possible). This is a change
in behaviour, which is under review. If it causes problems to you,
please let us know.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
threads.
Root cause is that libnet is not thread-safe. Omudpspoof now
guards libnet calls with their own mutex.
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and
full delayable sources somewhat smarter and permits, assuming sufficient
timouts, to persist message up to the max queue capacity. Also some nits
debug instrumentation have been fixed.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Note: "users" means modules, like imtcp and imdiag. NOT real users
or devices.
|
| | | |
| | | |
| | | |
| | | | |
... if more than 3 fds were to be read at the same time.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this also applied to other users of core file tcpsrv.c, but imtcp was
by far the most prominent and widely-used, the rest rather exotic
(like imdiag)
NOTE: this patch is probably not 100% correct and may cause problems
if multiple tcpsrv.c users existing within a configuration. The next
step is to evaluate this and probably slightly change the worker thread
startup/shutdown location.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I am not really sure if that is an issue at all, at least it
is inconsistent.
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \
| | | |/
| | |/|
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and
full delayable sources somewhat smarter and permits, assuming sufficient
timouts, to persist message up to the max queue capacity. Also some nits
in debug instrumentation have been fixed.
|
| | | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \ |
|
| | | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | /
| | | |/
| | |/| |
Conflicts:
ChangeLog
|
| | | | |
|
| | | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
Conflicts:
tools/syslogd.c
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This could lead to segfaults. Triggering condition: multiple action
instances using ommysql. Thanks to Tomas Heinrich for reporting this
problem and providing an initial patch (which my solution is based on,
I need to add more code to clean the mess up).
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...due to unvailable sources. Fixes:
http://bugzilla.adiscon.com/show_bug.cgi?id=299
Thanks to Marcin M for bringing up this problem and Andre Lorbach
for helping to reproduce and fix it.
|