| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This helps prevent message routing loops, and is vital to have
if omjournal is used together with traditional syslog.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
previously, hostname and ip strings were shuffled to the msg object, which
created a property out of them. Now the cache holds the property, and it
is resused (almost) everywhere, what saves a lot of memory operations.
The only exception is imtcp session setup, where different handling
of the hostname is done, which we need to sort out (but that's another
story).
|
| |
|
| |
|
|
|
|
| |
mutexes on systems without atomic instructions were incorrect
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Moave element status out of batch_obj_t because we
get a *much* better cache hit ratio this way.
Note that this is really a HUGE saving, even if it
doesn't look so (both profiler data as well as
practical tests indicate that!).
|
|
|
|
| |
also fixed a couple of smaller issues along that way
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
tools/omfile.c
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/msg.c
runtime/queue.c
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
tools/syslogd.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This happened only on very high volume systems, if the same message was
being processed by two different actions. This was a regression caused
by the new config processor, which did no longer properly enable msg
locking in multithreaded cases. The bugfix is actually a refactoring of
the msg locking code - we no longer do unlocked operations, as the use
case for it has mostly gone away. It is potentially possible only at
very low-end systems, and there the small additional overhead of doing
the locking does not really hurt. Instead, the removal of that
capability can actually slightly improve performance in common cases,
as the code path is smaller and requires slightly less memory writes.
That probably outperforms the extra locking overhead (which in the
low-end case always happens in user space, without need for kernel
support as we can always directly aquire the lock - there is no
contention at all).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The "queue.xxx" parameter set was not supported, and legacy ruleset
config statements did not work (by intention). The fix introduces the
"queue.xxx" parameter set. It has some regression potential, but only
for the new functionality. Note that using that interface it is possible
to specify duplicate queue file names, which will cause trouble. This
will be solved in v7.3, because there is a too-large regression
potential for the v7.2 stable branch.
|
| | |
| | |
| | |
| | |
| | | |
the changes do not affect actual code execution, just keep the
compile log clean.
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | | |
which could also mean "never" or "not for a very long time".
|
|\| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The indentation around the "-d" flag description is in the
wrong place and does not display properly.
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
this enables smoother builds on older systems that do not support
libuuid. Loss of functionality should usually not matter too much as
uuid support has only recently been added and is very seldom used.
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
| | | |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
a special ratelimiter is used; it's linux-type ratelimit settings
are currently hardcoded
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Conflicts:
ChangeLog
doc/v7compatibility.html
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
no actual implementation yet done
|
|\ \ \ \ \ \ \ \ \
| | |_|_|_|_|/ / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Conflicts:
configure.ac
doc/manual.html
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
We also added a testbench test to check for this in the future. That
in turn required new testbench tools.
|
|\| | | | | | | |
| |_|_|_|_|/ / /
|/| | | | | | | |
|