| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Conflicts:
tools/omfile.c
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I commented out some debug code that is only useful in some
testing scenarios and re-enabled the old code. This solved a FreeBSD
compile issue. Also, I fixed some other syntax error, which somehow
went into the tree (I am still puzzled about that, especially as some
have already and successfully build from that tree... anyhow ;)).
|
| | |
| | |
| | |
| | | |
Enables to use FQDNs in sender names where the legacy default
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
doc/rsyslog_conf.html
plugins/imudp/imudp.c
runtime/rsyslog.h
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The legacy ACL system needs access to the remote sockaddr_storage
data structure. This has been implemented for the ptcp driver and
now follows for gtls. See recent commits for reason.
We also moved up the version numbers in preparation of the release.
|
| | | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
|
| | |
| | |
| | |
| | | |
...all senders were permitted instead
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
The format is based on what Cisco devices seem to emit.
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
doc/property_replacer.html
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
doc/manual.html
|
| | |
| | |
| | |
| | |
| | |
| | | |
This allows to return the string 0 if a regular expression is
not found. This is probably useful for storing numerical values into
database columns.
|
| | |
| | |
| | |
| | |
| | |
| | | |
RE's seem to be a big trouble spot and I would like to have more
information inside the debug log. So I decided to add some additional
debug strings permanently.
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | | |
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
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | | |
- 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
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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.
|
|\| | |
|
| |\| |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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).
|