| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | | |
Thanks to Zdenek Salvet for finding this bug and to Bodik for reporting
|
| | |
| | |
| | |
| | | |
For the time being, $uptime is not supported on Solaris
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
due to a problem with boolean shortcut operations. From the user's
perspective, the segfault is almost non-deterministic (it occurs when
a shortcut is used).
Thanks to Lars Peterson for providing the initial bug report and his
support in solving it.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/modules.c
|
| |\ \ \
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/modules.c
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If it is not present, it must have the nilvalue "-" as of RFC5424
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=332
Thanks to John N for reporting this issue.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=316
Thanks to Andreas Piesk for reporting&analyzing this bug as well as
providing patches and other help in resolving it.
|
| | | |
| | | |
| | | |
| | | | |
also added some error checking
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There seem to be cases where the shutdown message is otherwise not
processed, not even on an idle system. Thanks to Marcin for
bringing this problem up.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The plugin now uses libmongo-client (which is configured using
pkg-config) instead of the 10gen client, so the instructions to copy
client source code no longer apply.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The problem was introduced by the fix I did roughly an hour ago.
Obviously, no released version is affected.
|
| | | |
| | | |
| | | |
| | | | |
so that we have cleaner code
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
traditional system line buffers were not freed. semi-static memory leak
during config load phase, did not grow while processing messages. Usually
less than 5k during the whole runtime.
|
| | | |
| | | |
| | | |
| | | | |
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.
|