| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
|
| |
| |
| |
| |
| | |
This and the other patch from Martin (this morning) was released
under ASL 2.0 by him.
|
| |
| |
| |
| | |
present.
|
| | |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
plugins/omudpspoof/omudpspoof.c
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
it now truncates these message, but ensures they are sent. Note that
7.2.5+ will switch to fragmented UDP messages instead (up to 64K)
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On-the-fly compression support code was present since the initial
module was written, however, no config options existed to actually
activate it. I have now removed that code for clarity (obviously
there is no need to maintain it or add the feature - nobody ever
complained in the past...)
|
| | | |
| | | |
| | | |
| | | | |
retains bugfix while increasing performance again
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a brute-force troubleshooting aid. Will later be changed to
better code.
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
On Ethernet, they need to be transmitted in multiple fragments. While
it is known that fragmentation can cause issues, it is the best choice
to be made in that case. Also improved debug output.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Use LT_LIB_M to find the math library which is needed for pow().
|
| | |
| | |
| | |
| | | |
Released under ASL 2.0, permission given via email.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
registered
This lead to a "module not found" error message instead of
the to-be-expected "module does not support new style" error message.
That invalid error message could be quite misleading and actually stop
people from addressing the real problem (aka "go nuts" ;))
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | |
| | | |
This is based on Marius Tomaschewski's set of patches, mostly
just applied manually (as I need to mangle with the merge).
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note: this was not a simple merge, I rather needed to adopt the v5 code to
the new v6 config handling. However, no v6 config format has been added yet
(this is the next step).
Conflicts:
plugins/imklog/imklog.c
plugins/imklog/imklog.h
|
| | |
| | |
| | |
| | |
| | |
| | | |
... actually, they are microseconds. So the fractional part of the
timestamp was not properly formatted.
Thanks to Marius Tomaschwesky for the bug report and the patch idea.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When enabled, kernel message [timestamp] is converted for message time.
Default is to use receive time as in 5.8.x and before, because the clock
used to create the timestamp is not supposed to be as accurate as the
monotonic clock (depends on hardware and kernel) resulting in differences
between kernel and system messages which occurred at same time.
|
| | |
| | |
| | |
| | |
| | | |
When enabled, the kernel [timestamp] remains at begin of
each message, even it is used for the message time too.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is not a real problem (thus no ChangeLog entry): we leaked a few
bytes for every relp listener, but only at rsyslogd TERMINATION - where
obviously the OS does the cleanup. However, the leak could cause some
confusion with memory checkers like valgrind.
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=380
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | |
| | | |
This had no bad effect, because the macro did the same as the one
that should have been used.
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
On many platforms, this has no effect at all. At some, it may cause
a segfault. The problem occurs only during config phase, no segfault
happens when rsyslog has fully started.
|
| |\ \ |
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
closes (for v7.2): http://bugzilla.adiscon.com/show_bug.cgi?id=366
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
... because action-like statements in action lists are not supported
in 7.1. This will be available in 7.3, but it is too late to do this in
7.1. So we disable the warnings and re-enable them in 7.3. Functionality-
wise, this is no problem at all as the legacy constructs are still
fully supported.
Thanks to forum user "canadaboy" for mentioning this problem.
|