| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
|
|
|
|
|
| |
...which enables to configure HUP to be either a full restart
or "just" a leightweight way to close open files
|
|
|
|
|
|
| |
...to enable users to turn off pthread_yield calls which are
counter-productive on multiprocessor machines (but have been
shown to be useful on uniprocessors)
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
|
| |
| |
| |
| |
| | |
plus solving a compile problem for im3195 (which is not used
in practice, thus this did not show up before...)
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
- if queues could not be drained before timeout - thanks to
David Lang for pointing this out
- added link to german-language forum to doc set
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |\|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\| |
|
| | |\ |
|
| | | |\
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
syslogd.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Thanks to Frederico Nunez for providing the fix. The actual patch
was commited before this one - unfortunately I forgot to set
the author correct when commiting it and then it was pushed to
the online repository. Sorry for this ;)
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- a big one in syslogd.c, which caused messages not to be
freed when compiled for single-threading mode
- a small one in the file output handler, outchannels, when
a size-reached action was to be executed
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This occured if queues could not be drained before timeout.
Thanks to David Lang for pointing this out.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This enables us to use more efficient calling conventions and
also helps us keep the on-disk structure of a msg object more
consistent in future releases.
|
|\| | | | |
|
| |\| | | |
|
| | |\| | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
if queue size reached light_delay mark, enqueuing
could potentially be blocked for a longer period of time, which
was not the behaviour desired.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
which so far seems to increase performance. There is also
reason for it to do so, see http://kb.monitorware.com/post14216.html#p14216
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I tried to work too quick this morning. A side-effect of an
earlier change was that no UDP messages were parsed, which
lead to their loss, because no PRI was set in this case.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Message parsing is now done as part of main message queue worker
processing (was part of the input thread) This should also improve
performance, as potentially more work is done in parallel.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
cleaned up previous code and redid it in a way that makes
it much easier to extend it
also added a new macro DBGPRINTF which is a performance-optimzed
version of dbgprintf
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This enhances performance and, as some have pointed out, is
probably also more consistent with what users expect how
the various output-timestamp related function should work. This
commit needs some more testing.
|
| | | | |
| | | | |
| | | | |
| | | | | |
the critical section what could so with acceptable consequences
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...which enables to work with
less acurate timestamps in favor of performance. This enables querying
of the time only every n-th time if imudp is running in the tight
receive loop (aka receiving messsages at a high rate)
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
|
| |\| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
if that timestamp did not contain any subsecond information (the
resulting string was garbagge but should have been "0", what it now is).
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...this improves performance and consistency and also fixes
a bug where subsecond time properties generated by imfile, imklog and
internal messages could be slightly inconsistent.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
removed code not actually needed in imupd
|
|\| | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | |\| | | |
|
| | | |\| |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
runtime/net.c
|