| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
if systemd writes a kernel log entry with a non-kernel priority,
the priority recorded in the kernel log will be wrong. However,
it will be immediately followed by another priority (with the
kernel timestamp in between, if enabled). So imklog now tries
to see if there is a second PRI and, if so, uses it. Note that
we already support non-kernel PRIs in the kernel log, as this
was done in BSD for quite some while. HOWEVER the config
statement "$klogpermitnonkernelfacility on" must be used to
permit this (otherwise non kernel messages are dropped).
Sample of a such a message on a kernel without timestamping
enabled:
$ echo '<14>text' > /dev/kmsg
$ dmesg -r
<4><14>text
NOTE: support for timestamp is NOT YET ENABLED!
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
this was due to improper parsing of ":"
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=250
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
also, config statements were named a bit inconsistent, resolved that
problem by introducing an alias and only documenting the consistent
statements
Thanks to Marcin for bringing up this problem.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... to select if tcp received messages shall be flagged as
light delayable or not.
|
|\| | |
| |_|/
|/| |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | |
| | | |
The test is a setup scenario for this bug tracker:
http://bugzilla.adiscon.com/show_bug.cgi?id=241
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
to facilitate testing
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
still some questions outstanding, so actual SQL statement is
not usable at the moment
|
| | |
| | |
| | |
| | |
| | |
| | | |
because the sql/stdsql option could not be specified. This has been
solved by permitting the strgen to include the opton inside its name.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=195
|
| | |
| | |
| | |
| | |
| | | |
bug http://bugzilla.adiscon.com/show_bug.cgi?id=195
That bug currently prevents strgen's to be used with databases
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This had no real consequences, as it happend exactly
once during the runtime, so the OS cleaned up. However, it
broke the valgrind testbench.
|
|\| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
epoll_create1() was introduced in Linux kernel 2.6.27. If rsyslog was
compiled on a newer kernel but run on a kernel older than 2.6.27, remote
syslog fails. Apply a runtime check for epoll_create1() and fall back to
epoll_create() in this case.
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617996
|
| | |
| | |
| | |
| | |
| | | |
also testbench improvement (omlibdbi now also receives a couple of
tests if we have a life MySQL server).
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| |\ \ |
|
| | |\| |
|
| | | |
| | | |
| | | |
| | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=203
|
|/ / /
| | |
| | |
| | |
| | | |
as we now call the HDFS API with much larger message
sizes and far more infrequently
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The capability has been added for module to specify that they do not
like being unloaded.
related bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=222
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
The previous fix left variable lenMsg in an inconsistent state when
sanitization actually happend. This could lead to message truncation.
|
| | |
| | |
| | |
| | |
| | | |
This also causes problems when NUL characters are present inside
the message (as is the case with spamd).
|
| | |
| | |
| | |
| | | |
thanks to Michael Biebl for alterting me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was a regression from the imuxsock partial rewrite. Happened
because the message is no longer run through the standard parsers.
Now imuxsock does this sanitization itself.
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=224
|
| | |
| | |
| | |
| | |
| | |
| | | |
we do this directly in the beta because a) it does not affect existing
functionality and b) one may argue that this missing functionality is
close to a bug.
|
| | |
| | |
| | |
| | |
| | |
| | | |
circumstances
This has now been solved, at least for common situations.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Support for multiple unix sockets and activation in forking mode
Signed-off-by: Marius Tomaschewski <mt@suse.de>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
when removing text from the message, decrement the length when you increment
the pointer through the message. there were a number of places where this was
missed.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|