| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/rsyslog.h
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
(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
|
| | |\|
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
tests/diag.sh
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
The enhanced testbench now runs without failures, again
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
also changed DA queue mode in that the regular workers now run
concurrently.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... in preparation for some larger changes - I need to apply some
serious design changes, as the current system does not play well
at all with ultra-reliable queues. Will do that in a totally new version.
|
| | | | |
| | | | |
| | | | |
| | | | | |
slightly improved situation, would like to save it before carrying on
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... and now make check fails again, we have obviously found some new
bugs thanks to the additional cases
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
tests/Makefile.am
tests/diskqueue.sh
tests/imtcp-multiport.sh
tests/manytcp.sh
tests/memq-persist.sh
|
| |\| | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... and also improved the test suite. There is a design issue in the
v3 queue engine that manifested to some serious problems with the new
processing mode. However, in v3 shutdown may take eternally if a queue
runs in DA mode, is configured to preserve data AND the action fails and
retries immediately. There is no cure available for v3, it would
require doing much of the work we have done on the new engine. The window
of exposure, as one might guess from the description, is very small. That
is probably the reason why we have not seen it in practice.
|
| | | | | |
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
tests/Makefile.am
|
| |\| | | |
|
| | | | | |
|