| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\| | |
|
| | |\| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- bugfix: invalid error message issued if $inlcudeConfig was on an empty
set of files (e.g. *.conf, where none such files existed)
thanks to Michael Biebl for reporting this bug
- bugfix: when run in foreground (but not in debug mode), a
debug message ("DoDie called") was emitted at shutdown. Removed.
thanks to Michael Biebl for reporting this bug
- bugfix: some garbagge was emitted to stderr on shutdown. This
garbage consisted of file names, which were written during
startup (key point: not a pointer error)
thanks to Michael Biebl for reporting this bug
- bugfix: startup and shutdown message were emitted to stdout
thanks to Michael Biebl for reporting this bug
|
| | | | |
|
| | | |
| | |
| | |
| | | |
stderr and stdo are now kept open across fork()
|
| | | |
| | |
| | |
| | |
| | | |
... as well as some cleanup (some commented-out code is left to
support UxTradMsg again is someone really complains ;)).
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
- saved gettimeofday() calls in imtcp (and increased reception buffer)
- somewhat optimized stringbuf.c
- some other optimizations
|
| | | |
| | |
| | |
| | |
| | |
| | | |
this does not mean the v4 engine will support batches and output
transactions, but I can now write plugins that will work equally well
with v4 AND v5. I consider this useful during the rewrite of omfile.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
this permits us to keep a persistent test environment between
v4 and v5, most importantly using the same tools. As far as the
actual tests are concerned, some had issues. I had no time to check
if that was an issue with the test or an actual issue with the
v3/4 engine. Will do that at some later stage.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
(in addition to rather specific syslog tcp server)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
... this provides some basic support to integrate extensions that
are not direct parts of rsyslog to be built during its build
process.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
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.
|
| |\| | | |
|
