| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This is kind of a bugfix, but a very intrusive one, thus it goes
into the devel version first. Right now, "file not found" is
handled and leads to the new emergency mode, in which disk action
is stopped and the queue run in direct mode. An error message is
emited if this happens.
|
| |
|
|
|
|
|
|
|
|
| |
This make the privilege drop code more bulletproof, but breaks Ubuntu's
work-around for log files created by external programs with the wrong
user and/or group. Note that it was long said that this "functionality"
would break once we go for serious privilege drop code, so hopefully
nobody still depends on it (and, if so, they lost...).
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
| | | |
| | | |
| | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=233
|
|\| | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
plus bump to new v5-stable
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It has proven to be very valuable, so now it is properly formatted
inside the source.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Marius Tomaschewski <mt@suse.de>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Note that this actually is a very small change, but I needed
to shuffle a lot of code around in order to make it compile
(due to required define order...).
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... to select if tcp received messages shall be flagged as
light delayable or not.
|
|\ \ \ \ \
| | |/ / /
| |/| | /
| |_|_|/
|/| | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
After trying out some more things with the new code (after last
bugfix), I now think that the bugfix is OK to use and without
regressions.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
potentially closes: http://bugzilla.adiscon.com/show_bug.cgi?id=241
But needs more verification.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The test is a setup scenario for this bug tracker:
http://bugzilla.adiscon.com/show_bug.cgi?id=241
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this was due to the old RFC5424 parser being considered correct,
what it was not. As such, the samples generated from it were
incorrect as well. Now with the corrected parsers, the tests failed.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
to facilitate testing
|
| | | | |
| | | | |
| | | | |
| | | | | |
...(just like a failed filter)
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=243
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: root <root@localhost.localdomain>
|
| | | | | | |
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=237
|
| |/ / /
| | | |
| | | |
| | | | |
needs testig and verification (wrong system for doing that ;))
|
| | | | |
|
| | | | |
|