| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
...what could lead to problems in other parts of the code
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.ac
doc/manual.html
plugins/imfile/imfile.c
plugins/imklog/bsd.c
plugins/imklog/imklog.c
plugins/imklog/imklog.h
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/ /
| |
| |
| |
| | |
Thanks to Marius Tomaschweski for the suggestion and a patch (for v5)
that this commit bases on.
|
| |\|
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
| |\|
| |
| |
| |
| |
| | |
Conflicts:
plugins/imklog/ksym.c
plugins/imklog/linux.c
|
| |/
|
|
|
|
|
| |
The Linux driver no longer supports outdated kernel symbol resolution,
which was disabled by default for very long. Also overall cleanup,
resulting in much smaller code. Linux and BSD are now covered by a
single small driver.
|
| |
|
|
|
|
|
| |
If the kernel time-stamps messages, time is now take from that
timestamp instead of the system time when the message was read. This
provides much better accuracy. Thanks to Lennart Poettering for
suggesting this feature and his help during implementation.
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.ac
runtime/cfsysline.c
tools/ompipe.c
|
| | | |
|
| |/
|
|
|
|
|
|
| |
support for enhancing probability of memory addressing failure by
using non-NULL default value for malloced memory (optional, only if
requested by configure option). This helps to track down some
otherwise undetected issues within the testbench and is expected
to be very useful in the future.
|
| | |
|
| | |
|
| |
|
|
|
| |
The limit can now be set via $MaxMessageSize global config
directive (finally gotten rid of MAXLINE ;))
|
| | |
|
| |
|
|
|
|
| |
- implemented $KLogInternalMsgFacility config directive
- implemented $KLogPermitNonKernelFacility config directive
- modified internal interfaces
|
| |
|
|
|
|
|
| |
This obviously happens on BSD (<118> markers seen). We now have the ability
to allow or prevent it, with the default being not permitted. Should not at
all affect other drivers, but it is implemented on a common code basis,
not on the driver layer.
|
| |
|
|
|
|
| |
bsd.c uses strchr, strlen and memmove, so include string.h
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
|
| |
|
