| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
another milestone commit: the program works, the new interface
is used, some more cleanup is needed and the per-ruleset config
options are still missing. But we are getting closer...
|
|
|
|
|
| |
This is a milestone commit, which adds new code that breaks
nothing, but also does not add any visible change. Just prep work...
|
|
|
|
|
|
| |
I cleaned up a lot of config variable access along the way. This
version compiles and runs, but does not yet offer any enhanced
functionality. pmrfc5424 is just a dummy that is not yet being used.
|
|
|
|
|
|
| |
processing.
THIS IS A VERY IMPORTANT ADDITION, see its doc for why.
|
|
|
|
|
| |
This offers considerable additional flexibility AND superior performance
(in cases where multiple inputs now can avoid lock contention)
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/rsyslog.h
tcpsrv.c
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
|
| | | |
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
configure.ac
doc/manual.html
runtime/datetime.h
runtime/parser.c
runtime/rsyslog.h
tools/syslogd.c
v4-stable had a bug with RFC5424-formatted structured data, which showed
was detected by the enhanced automatted testbench of v4-beta.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is now a "good" rsyslog output module, working as usual. I've also
sorted out some reentrency issues. Code is clean and ready to be tested
in practice ;)
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
some things inside the message can be used over a large number of
messages and need to to be allocated and re-written every time. I now
begin to implement this as a "prop_t" object, first use for the inputName.
Some input modules are already converted, some others to go. Will do
a little performance check on the new method before I go further.
Also, this commit has some cleanup and a few bug fixes that prevented
compiliation in debug mode (I overlooked this as I did not compile
for debug, what I normally do, and the automatted test also does not
do that)
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
|
| | | |
|
|\| | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... hopefully removes false positives (but may cause some trouble
with hostname parsing). For details, see this bug tracker:
http://bugzilla.adiscon.com/show_bug.cgi?id=126
This patch is not optimal for v4 - another one will follow. The spirit
of this commit is to enable easier backporting if someone is interested
in doing so.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- done malloc() instead of calloc() for msg_t, as we have large space
which needs not be initialized
- shrunk syslogTime structure in the hope to get better cache and
write performance (non-aligned data should not hurt much here)
|
|\| | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was a complex manual merge, especially in action.c. So if
there occur some problems, this would be a good point to start
troubleshooting. I run a couple of tests before commiting and
they all went well.
Conflicts:
action.c
action.h
runtime/queue.c
runtime/queue.h
runtime/wti.c
runtime/wti.h
|
| | |
| | |
| | |
| | |
| | | |
will fill this with live somewhat later, noticed I need to do some stage work
first (at least this is useful).
|
| | |
| | |
| | |
| | | |
... commit before I try to touch the queue side ;)
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that this was NOT a trivial merge, and there may be
some issues. This needs to be seen when we continue developing.
Conflicts:
runtime/msg.h
runtime/obj.h
runtime/queue.c
runtime/srUtils.h
runtime/stream.c
runtime/stream.h
runtime/wti.c
tests/Makefile.am
tools/omfile.c
tools/syslogd.c
|
| | | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
runtime/msg.h
tcps_sess.c
tcpsrv.c
tools/syslogd.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
- saved gettimeofday() calls in imtcp (and increased reception buffer)
- somewhat optimized stringbuf.c
- some other optimizations
|
| | |
| | |
| | |
| | | |
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 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.
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This DOES NOT work sufficiently well, I just wanted to verify that
zip writing is possible and files are readable. Will be refined
soon.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
tests/Makefile.am
|
| |/
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/rsyslog.h
|
| |
| |
| |
| | |
(in addition to rather specific syslog tcp server)
|
| |\
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | | |
| | | |
| | | | |
slightly improved situation, would like to save it before carrying on
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... 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.
|