| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\ |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
rsyslog.service.in
|
| | |
| | |
| | |
| | |
| | |
| | | |
both from code & doc and emitted warning message if still used
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=361
Thanks to Michael Biebl for reporting & suggestions
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With the introduction of the journal in systemd v38 [1], the
systemd-kmsg-syslogd.service service was removed. All major
distributions which ship systemd use v44 or later in their current
releases, so it seems safe to drop the ExecStartPre command.
[1] http://lists.freedesktop.org/archives/systemd-devel/2012-January/004188.html
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In v6 [1], the compatibility mode has been removed and -c is a basically
a no-op. So just drop that obsolete command line flag.
[1] http://www.rsyslog.com/doc/v6compatibility.html
|
| | | |
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imuxsock/imuxsock.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This happened only under some circumstances. Thanks to Marius
Tomaschwesky, Florian Piekert and Milan Bartos for their help in
solving this issue.
Note that Milan sent a patch, which solved the problem under some
conditions (can be found somewhat earlier in git history). However,
it did not handle the original root cause, and so did not fix the
problem always. The main reason was that the date parser modifies
the provided lenghts. That part of the API was not properly
used by the caller (who decremented the length once more).
|
| | |
| | |
| | |
| | | |
modified: plugins/imuxsock/imuxsock.c
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
plugins/mmjsonparse/mmjsonparse.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
CEE originally specified the cookie with SP, whereas other lumberjack
tools used it without space. In order to keep interop with lumberjack,
we now use the cookie without space as well. I hope this can be changed
in CEE as well when it is released at a later time.
Thanks to Miloslav Trmač for pointing this out and a similiar v7 patch.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The only mention of @cee: in the Lumberjack pages,
https://fedorahosted.org/lumberjack/wiki/FieldList doesn't have a space,
and libumberlog does not in fact generate one.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
E.g. in
> set $!time = $timereported;
> set $!time_rcvd = $timegenerated;
pTpe is set to NULL by the caller.
(Is "default" the correct format to use?)
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
as this module's functionality has been superseeded by the "call"
statement.
Thanks to Michael Biebl for alerting me on the still-old default.
|
| | | |
|
| | |
| | |
| | |
| | | |
action object was created twice, resulting in memleak
|
| | |
| | |
| | |
| | |
| | | |
- bugfix: small memory leak when processing action() statements
- bugfix: unknown action() parameters were not reported
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This behaviour is OK for "contains"-type of comparisons (which have quite
different semantics), but not for == and <>, which shall be commutative.
This has been fixed now, so there is no difference any longer if the
constant string array is the left or right hand operand. We solved this
via the optimizer, as it keeps the actual script execution code small.
|
| | |
| | |
| | |
| | | |
This is no longer needed.
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
plugins/cust1/Makefile.am
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for identifying this as the culprit for
several build-related issues. The plugin is a placeholder, and was
not used for quite some while. It is definitely not worth the effort
to keep it along. If needed, can be quickly created.
|
| | |
| | |
| | |
| | | |
libtool archives are not meant to be shipped in the source tarball.
|
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for alerting me of the problem.
|
|\| | |
|
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for alerting me of the problem.
|