| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In async write mode, we use modular arithmetic to index the output
buffer array. However, the counter variables accidently were signed,
thus resulting in negative indizes after integer overflow. That in turn
could lead to segfaults, but was depending on the memory layout of
the instance in question (which in turn depended on a number of
variables, like compile settings but also configuration). The counters
are now unsigned (as they always should have been) and so the dangling
mis-indexing does no longer happen. This bug potentially affected all
installations, even if only some may actually have seen a segfault.
|
| | | | |
| | | |
| | | |
| | | | |
Some devices seem to create them and I do not see any harm in supporting that.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is for another prctl() call, not present in the beta version (looks like it
would make sense to stick these into a utility function)
|
| |\ \ \ \ |
|
| | | | | | |
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We are doing this to support removal of restart-type HUP in v5.
Elaborate doc added to explain reasoning and actions to be taken.
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
(double free)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
optimized substring processing, should bring a small enhancement when
forwarding with the default forwarding templates. Also did some uchar
cleanup in msg.c (thus so many changes, in reality they are few...).
|
| |\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
tests/nettester.c
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This was a result of an internal processing error if maximum field
sizes had been specified in the property replacer.
Also did some testbench improvements, including omstdout.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
for the stream class and thus finally activating omfile's timeout
capability in a useful way without polling and too-high performance
overhead.
|
| | | | | | |
|
| |\| | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
... when working with disk queues.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... this is necessary in preparation for the final solution (we need
to have a "unified" writer). If it causes worse performance to have the
zip writher togehter with the synchronous write, we may do an async write...
|
| | | | | | |
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(depending on configuration). This was a small change, but with big
results. There is more potential to explore, but the effects were so
dramatic that I think it makes sense to include this fix.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
... seems to work on quick testing, but needs a far more testing
and improvement. Good milestone commit.
|
| | | | |
| | | |
| | | |
| | | | |
Happend e.g. with imuxsock.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This could lead to timestamps written in the wrong format, but not to
an abort.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... hopefully reducing the number of allocs/frees as well as overall
memory usage in a busy system (plus that these shared properties hopefully
remain in cache longer than its single-instance counterparts...)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This sets stage to enable use of the property-interface to speed
up things (mildly), the next step to be done. I have also fixed one
regression of yesterday's changes.
|
| | | | |
| | | |
| | | |
| | | | |
... because LARGFILE macros were not defined consistenly
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... plus a fix for a long-time bug in obj-types.h. That lead to
the object pointer only then to become NULL when the object was
actually destructed, I discovered this issue during
introduction of the pRcvFrom property in msg_t, but it potentially had other
effects, too. I am not sure if some experienced instability resulted from this
bug OR if its fix will cause harm to so-far "correctly" running code. The later
may very well be. Thus I will change it only for the current branch and also
the beta, but not in all old builds. Let's see how things evolve.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
... plus some celanup and adding minor missing functionality
(the rule debug info again tell the property name, not just number).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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)
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
inline
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
... but I don't see the name anywhere...?
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
... this one could cause trouble, but I really don't think it caused
any actual harm.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- bugfix: subtle (and usually irrelevant) issue in timout processing
timeout could be one second too early if nanoseconds wrapped
- set a more sensible timeout for shutdow, now 1.5 seconds to complete
processing (this also removes those cases where the shutdown message
was not written because the termination happened before it)
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
... as far as I think this mostly is to keep the thread debuggers
happy
|
| |\ \ \ \ |
|
| | |\| | |
| | |/ /
| |/| | |
|
| | | |\| |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Detected under threading debugger, seems not to have any impact on
actual deployments.
|
