| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Conflicts:
runtime/conf.c
|
| | |
| |
| |
| |
| |
| |
| |
| | |
sending n messages
New config directive $ActionSendUDPRebindInterval
added for the purpose. By default, rebinding is disabled. This is
considered useful for load balancers.
|
| |\ \
| |/
|/|
| |
| | |
Conflicts:
runtime/rsyslog.h
|
| | |\
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
|
| | | |
| | |
| | |
| | |
| | | |
... I know I should not have done this to a stable branch... Thankfully
nothing was yet released.
|
| | | | |
|
| |\| | |
|
| | |\| |
|
| | | |
| | |
| | |
| | | |
(testcase was only present in v4, so I did not spot the issue immediately)
|
| | |\|
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
| | |
| | |
| | | |
... as well as some other minor issues.
|
| | | | |
|
| |\| |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | |\|
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
is detected.
This change is considered important but small enough
to apply it directly to the stable version. [But it is a border case,
the change requires more code than I had hoped. Thus I have NOT tried
to actually catch all cases, this is left for the current devel
releases, if necessary]
|
| | | |
| | |
| | |
| | |
| | |
| | | |
...when rsyslogd ran in forked mode (as usual!)
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
after confirmation from the field that this version is sufficient.
I always thought so (I think I developed under 1.4.x), but had no
longer an environment to verify. Most imporantly, this means that
Centos users will have much less trouble building rsyslog/tls
support.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
specified.
Thanks to Michael Biebl for helping to debug this one.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Include <string.h> for memcpy and strlen.
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| |\| | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The imdiag module now can very effectively inject messages, which also
frees us from uncertainties of tcp reception and processing. All shell
script based tests have been modularized, what makes it far easier to
create new tests. Also, the test bench now executes more reliable and
much faster, because we can now rely on actual engine information where
we previously did just a dumb sleep.
|
| |\| | | |
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
imdiag/imtcp had a modload race condition (as imdiag is a testing aid,
this has no implications for production deployments). Also, I replaced
netcat by a custom program to talk to imdiag. This, for the first time ever,
is now a Java program. I plan to add some GUI troubleshooting tools and
thought it is a good idea to start doing things in Java that can simply
be done in that language.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
which enables to talk to the rsyslog core at runtime. The current
implementation is only a beginning, but can be expanded over time
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Well, actually this and a lot of related things. I improved the
testbench so that the new capabilities are automatically tested and
also did some general cleanup. The current multiple tcp listener
solution will probably receive some further cleanup, too, but looks
quite OK so far. I also reviewed the way tcpsrv et all work, in
preparation of using this code for imdiag. I need to document the
findings, especially as the code is rather complicated "thanks" to
the combination of plain tcp and gssapi transport modes.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
imdiag was never finished (not even really begun), but now I need it.
I made the few things that are available compile, but more serious
work is required.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Use 2 new lines as separator between configure options.
- Remove forgotten copy&paste text.
- Reorder and move template configure option to the end.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Improve readability of the ./configure output by grouping relevant entries and
indenting them.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Be consistent and rename the configure variable want_gssapi_krb5 to
enable_gssapi_krb5.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only run omod-if-array.sh and parsertest.sh test if omstdout plugin is
enabled.
Remove the comment and fix the help output for --enable-stdout (default
was "no", not "yes")
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
include <string.h> for memcpy and strlen.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This file is useful for building rsyslog from git.
It is a shortcut for
autoreconf and ./configure and enables shave by default.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
shave tranforms the verbose autotools output into a pretty Kbuild-like
one which makes it easier to spot warnings.
See also
http://damien.lespiau.name/blog/2009/02/18/shave-making-the-autotools-output-sane/
git clone git://git.lespiau.name/shave
By default, shave is disabled and you have to explicitly enable it via
./configure --enable-shave.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- added $GenerateConfigGraph configuration command which can be used
to generate nice-looking (and very informative) rsyslog configuration
graphs.
- added $ActionName configuration directive (currently only used for
graph generation, but may find other uses)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the database rejected some entry, making the statement fail on it,
the batch was not cleaned and the same values were retried over and
over, causing a cascade of failures and a denial of service.
We use now OCI_BATCH_ERRORS so that everything valid in the batch is
inserted, and rejected values can be discarded.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of reading a complete line, we'll use a template and delegate
in the core to read such template. Then, all omoracle has to do is to
find that template and use it as the prepared statement.
I'm not sure if this is the correct approach, though. It has to dig
too much into rsyslog's structures...
txt_statement is stored in a private area, so that we don't mess too
much with rsyslog's internals (I still don't feel comfortable with
this much digging into template structures).
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This directive controls the amount of memory needed for properties in
the batch. Users should specify the largest value they expect in the
statement. As per Rainer's comment:
on MAX_BUFSIZE: I'd tend to make this configurable, because with
RFC5424 messages can be much longer and RFC5425 now recommends a
minimum maximum size of 8K.
So we let users to choose. Maybe we need a sensible default value to
make users' lifes easier?
Also, the old non-vector based interface is not supported anymore. I
broke it already when moving to this stage.
|
