| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
which so far seems to increase performance. There is also
reason for it to do so, see http://kb.monitorware.com/post14216.html#p14216
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|\| | |
|
| | | |
|
| |\ \ |
|
| | |\| |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/net.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
problem source is that getnameinfo() is not cancel-safe,
not that it is not thread-safe. It is now guarded against
cancellation.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... but removed the mutex, as the problem seems to be in cancel
processing, so the mutex is no longer necessary
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- changed sequence when awakening thread
- removed no longer needed condition variable
- EXPERIMENTALLY added mutex guarding to hostname lookups
this is to be removed if it does not have any verifyable
useful effect
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
- removed newly-introduced potential deadlock in debug system
- removed unnecessary pthread_cond_signal
- a bit general cleanup
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/debug.c
|
| | | |
|
| | |
| | |
| | |
| | | |
multi-threading
|
| | |
| | |
| | |
| | |
| | |
| | | |
destructor not yet permitted because verification is
missing that a atomic opration is sufficient for the
job required
|
| | |
| | |
| | |
| | |
| | | |
The code was potentially race, at least on systems where
a memory barrier was needed. Fix not fully tested yet.
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There was a wrong order of mutex lock operations. It is hard to
believe that really caused problems, but in theory it could and with
threading we often see that theory becomes practice if something is only
used long enough on a fast enough machine with enough CPUs ;)
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
removed
thanks to David Lang for his excellent performance analysis
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/rsyslog.h
tools/syslogd.c
|
| |
| |
| |
| |
| | |
This probably happened during a branch merge and was not detected.
Fixed now, should not haved any harm.
|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/datetime.h
runtime/rsyslog.h
|
| |
| |
| |
| |
| |
| |
| |
| | |
- added message property "inputname", which contains the name of the
input (module) that generated it. Presence is depending on suport in
each input module (else it is blank).
- added system property "$myhostname", which contains the name of the
local host as it knows itself.
|
| |
| |
| |
| |
| |
| |
| | |
Multiple immediately successive field delimiters are treated as
a single one.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |
| |
| |
| |
| | |
The limit can now be set via $MaxMessageSize global config
directive (finally gotten rid of MAXLINE ;))
|
| | |
|
| |
| |
| |
| |
| |
| | |
- bugfix: no error was reported if the target of a $IncludeConfig
could not be accessed.
- added testbed for common config errors
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- enhanced config file checking - no active actions are detected
- added -N rsyslogd command line option for a config validation run
(which does not execute actual syslogd code and does not interfere
with a running instance)
- somewhat improved emergency configuration. It is now also selected
if the config contains no active actions
- rsyslogd error messages are now reported to stderr by default. can be
turned off by the new "$ErrorMessagesToStderr off" directive
Thanks to HKS for suggesting these new features.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
doc/property_replacer.html
tools/syslogd.c
|