| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In systemd we now have a standard socket unit for /dev/log called
syslog.socket. This unit can be shared between an early boot mini syslog
and the full syslog implementation started later on. The mini syslog is
shipped along systemd and does nothing but simply forward the data
received through /dev/log to the kernel log buffer (i.e. kmsg, as
visible by dmesg). It is run during early boot, and then as soon as
rsyslog starts up it is terminated, so that rsyslog can take over the
/dev/log socket. Since one of the first things rsyslog does after
starting up is flushing the kernel log buffer to disk we end up with all
data from early boot up in syslog.
This patch changes two things: removes rsyslog.socket and instead
configures rsyslog.service to take possession of syslock.socket. And
secondly includes a PreStart line to terminate the running syslog bridge
instance.
|
|/ / / |
|
| | | |
|
| | |
| | |
| | |
| | | |
some cosmetic issues, plus a new valgrind-based test
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
tests/Makefile.am
tools/syslogd.c
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=232
|
| |\ \ |
|
| | | | |
|
| |/ / |
|
| | |
| | |
| | |
| | | |
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=217
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is kind of a backport of a similar UDP-based test from v6. However,
we do not have everything required for UDP in the v5 test tool base, so
we mimic the test with tcp -- which is not bad at all, because the
code path for TCP is somewhat different (and thus once we merge this
patch into v6, it is a useful addition).
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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>
|
|\ \ \ \ \
| |/ / / /
|/| | / /
| | |/ /
| |/| |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
a problem in the current testbench is that it depends on the locally
assigned system name. We have changed the default to the most common
default value. However, in the long term we need to fix this (and will
do so via a preloaded DNS cache, which we do not yet have!)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this could happen if multiple rulesets were used and some output batches
contained messages belonging to more than one ruleset.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=226
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=218
|
| | | |
| | | |
| | | |
| | | |
| | | | |
currently it generates only the power set, more work to do to make it
a real config generator.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
as well as potentially in a number of other places where MsgDup() was
used. This only happened when the imudp input module was used and it
depended on name resolution not yet had taken place. In other words,
this was a strange problem that could lead to hard to diagnose
instability. So if you experience instability, chances are good that
this fix will help.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this could happen if multiple rulesets were used and some output batches
contained messages belonging to more than one ruleset.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=226
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=218
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| |_|/ / /
|/| | / /
| | |/ /
| |/| | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | | |
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=225
|
| |/ /
|/| | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
control character escaping is now also being tested
|
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
|