| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| | |
- 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
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
it now works based on test case files, which enable to quickly
generate test cases.
|
| |
| |
| |
| |
| |
| | |
This is needed so that we can create simple testbenches which
will check the result of a test (a generated program) via a
simple strcmp.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
completed immediately.
While this sounds scary, the situation can not
happen in practice. We use non-blocking IO only for server-based gtls
session setup. As TLS requires the exchange of multiple frames before
the handshake completes, it simply is impossible to do this in one
step. However, it is useful to have the code path correct even for
this case - otherwise, we may run into problems if the code is changed
some time later (e.g. to use blocking sockets).
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
| |
| |
| |
| |
| | |
because the LOG_MAKEPRI() C macro has a different meaning there (it
is just a simple addition of faciltity and severity). I have changed
this to use own, consistent, code for PRI calculation.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/Makefile.am
doc/manual.html
|
| | |
|