| 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
|
| | | |
|
| |\| |
|
| | |\ |
|
| | | |\
| | | |
| | | |
| | | |
| | | |
| | | | |
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>
|
| |\| | | |
|
| | |\| | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
if queue size reached light_delay mark, enqueuing
could potentially be blocked for a longer period of time, which
was not the behaviour desired.
|
| |\| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
because getnameinfo() is not cancel-safe, but was not guarded against
being cancelled. pthread_cancel() is routinely being called during
HUP processing.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I am changing the way the version number is bumped so that
viewer git merge conflicts happen. In the future, it will
be bumped immediately before release and not immediately after
(though this means I need to be more careful with interim
versions).
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
|
| | | | | |
| | | | |
| | | | |
| | | | | |
multi-threading
|
| | |\ \ \ \ |
|
| | |\ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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 ;)
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | / / /
| | |_|/ / /
| |/| | | |
| | | | | | |
Conflicts:
doc/troubleshoot.html
|
| | |\ \ \ \ \
| | | |_|/ /
| | |/| | | |
|
| | | | | | | |
|
| |\| | | | |
| |_|_|/ /
|/| | | | |
|
| | |\| | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... as $...OnlyIfPrev... in some parts of the documentation. Thanks to
Lorenzo M. Catucci for reporting this bug.
|
| |\| | | |
| |_|/ /
|/| | | |
|
| | |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
It did not properly de-init a variable acting as a linked list head.
That resulted in trying to access freed memory blocks after the HUP.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
removed
thanks to David Lang for his excellent performance analysis
|
| |\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/rsyslog.h
tools/syslogd.c
|
| | |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
runtime/datetime.h
runtime/rsyslog.h
|
| | | |\|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
syslogd.c
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this caused a very minor issue with re-formatting a RFC3164 date when the
message was invalidly formatted and had a colon immediately after the date.
This was in the code for some years (even v1 had it) and I think it never
had any effect at all in practice. Though, it should be fixed - but definitely
nothing to worry about.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This has now been corrected. Required change to the
internal ParseTIMESTAMP3164() interface.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
resulting in strange operations.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
default discard severity was incorrectly set to 4, which lead
to discard-on-queue-full to be enabled by default. That could cause
message loss where non was expected. The default has now been changed
to the correct value of 8, which disables the functionality. This
problem applied both to the main message queue and the action queues.
Thanks to Raoul Bhatia for pointing out this problem.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Queue full is now -2074 and -2025 is unique again.
(did cause no real problem
except for troubleshooting)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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>
|
| | | | | |
|
