| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/msg.h
tcps_sess.c
tcpsrv.c
tools/syslogd.c
|
| | |
| |
| |
| |
| | |
... 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 is the first shot at this functionality. Currently, we run off a fixed
counter in the rsyslogd mainloop, which needs to be restructured. But this
code works, so it is a good time for a commit.
|
| | | |
|
| | |
| |
| |
| | |
a larger buffer is a cheap, yet useful, enhancement... ;)
|
| | |
| |
| |
| |
| | |
...by now using lowres time and thus saving many time() calls. This needs
some performance testing and must be made configurable if it works out.
|
| | |
| |
| |
| | |
... as well as added multi-ruleset support for imtcp
|
| | |
| |
| |
| | |
plus some cleanup...
|
| | |
| |
| |
| |
| |
| |
| | |
... by moving code to stream.c. Thanks to the new design, new cases are
not really needed, resulting in cleaner code.
I also did a cleanup of header file usage as a side-activity.
|
| | |
| |
| |
| |
| | |
this regression was introduced last friday, so this is *NOT* present
in any released version.
|
| | |
| |
| |
| | |
now contain a copy of the config line that (most likely) caused the error
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
so we now can define multiple rule sets, we just can not use them ;)
That means we have the foundation to bind listeners to different
rule sets.
|
| | |
| |
| |
| |
| |
| | |
... actually, it was not broken, but just very slow. I have now
reduced the number of test messages so that make check will not be
held for an extended period of time.
|
| | |
| |
| |
| | |
and another problem, both introduced today. Also did some general cleanup.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
... this was long overdue, and I finlly tackeld it. It turned out to
be more complex than I initially thought. The next step now probably is
to actually implement multiple rule sets and the beauty that comes
with them.
|
| | |
| |
| |
| |
| |
| |
| | |
also adds speed, because you do no longer need to run the whole file
system in sync mode. New testbench and new config directives:
- $MainMsgQueueSyncQueueFiles
- $ActionQueueSyncQueueFiles
|
| | |
| |
| |
| |
| |
| | |
... restoring missing functionality after the restructuring of imfile. As
a side-effect, this also lays the foundation for even more reliable queue
engine operations (but this is not yet done).
|
| | |
| |
| |
| |
| | |
now cleand up omfile and straighted out some things. The only commented-out
code left is code that must be moved/merged to the stream class, my next target.
|
| | |
| |
| |
| |
| |
| |
| | |
now only stream class is utilized. ttys, pipes and outchannel functionality
is currently disabled. But the testbench worked again. Cleanup needed, will
do this with next commit (it may break things and I like to have this
milestone here).
|
| | | |
|
| | |
| |
| |
| | |
now some basic operations are carried out via the stream class.
|
| | |
| |
| |
| |
| |
| | |
... and also made it callable via an rsyslog interface rather then
relying on the OS loader (important if we go for using it inside
loadbale modules, which we soon possible will)
|
| | |
| |
| |
| |
| |
| |
| | |
The former maximum of 10,000 really made no sense, even 1,000 is very high,
but we like to keep the user in control ;)).
Also, some general cleanup was done.
|
| |\| |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| | |
so they can now be processed with the "regular" gzip tools
|
| |/
|
|
|
|
| |
This DOES NOT work sufficiently well, I just wanted to verify that
zip writing is possible and files are readable. Will be refined
soon.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(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
|
