| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
... because action-like statements in action lists are not supported
in 7.1. This will be available in 7.3, but it is too late to do this in
7.1. So we disable the warnings and re-enable them in 7.3. Functionality-
wise, this is no problem at all as the legacy constructs are still
fully supported.
Thanks to forum user "canadaboy" for mentioning this problem.
|
|
|
|
|
| |
Thanks to Michael Biebl for mentioning this.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=364
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=365
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/nsdpoll_ptcp.c
|
| | | |
|
| | |
| | |
| | |
| | | |
plus some cleanup
|
|\| | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
curl has shipped that file since 2004.
|
| | |
| | |
| | |
| | |
| | | |
e2fsprogs resp. util-linux(-ng) have shipped that file since at least
2009.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Newer versions of pkg-config do that already. According to pkg-config
upstream this change was made around 2005, so it should be rather safe.
This change doesn't affect users building from dist tarballs anyway but
only if you are building from a Git checkout.
|
| | | |
|
| | | |
|
|\| | |
|
| | | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
|