| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
a kernel log message
This is an unusual case under Linux, and a frequent one under BSD
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
when parsing the config file. This is now corrected. Thanks
to Michael Biebl for pointing out the problem.
|
| | |
| | |
| | |
| | |
| | |
| | | |
thanks to varmojfekoj for the patch
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
A symbol file was closed when it couldn't opened. That lead to a
NULL pointer being passed to fclose()
|
| | | |
| | | |
| | | |
| | | | |
this callback is somewhat unportable in combination with dlopen()
|
| | | |
| | | |
| | | |
| | | | |
... and some cleanup
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | |
| | |
| | | |
Conflicts:
configure.ac
doc/manual.html
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
... (including segfault) on some platforms under some circumsances.
Thanks to Vieri for reporting this bug and helping to troubleshoot it.
|
| | |
| | |
| | |
| | | |
thanks to Michael Biebl for noticing
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
doc/manual.html
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
3.17.x is the new beta
Conflicts:
ChangeLog
configure.ac
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
plugins/imklog/imklog.c
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Thanks to Michael Biebl for pointing out that the kernel log did
not have them.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
bsd.c uses strchr, strlen and memmove, so include string.h
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's a hack, but at least it works now - on BSD. Will check later
if it is fine on Linux, too. Any better method of doing things is
happily accepted ;)
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
imklog now uses os-specific drivers. The initial "set" contains
the linux driver. This is a prequisite for BSD klog, which can
now be implemented on that driver interface.
|
| | | |
| | | |
| | | |
| | | | |
renamed to OS_BSD
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/ommail.html
queue.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Those with a space in front of the timestamp - at least HP procurve is
known to do that and I won't outrule that others also do it. The
change looks quite unintrusive and so we added it to the parser.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
GNU/Hurd does not define it (because it has no limit), and we have taken
care for cases where it is undefined now. However, some very few places
remain where IMHO it currently is not worth fixing the code. If it is
not defined, we have used a generous value of 1K, which is above IETF
RFC's on hostname length at all. The memory consumption is no issue, as
there are only a handful of this buffers allocated *per run* -- that's
also the main reason why we consider it not worth to be fixed any further.
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
configure.ac
|
| |\ \ \ \ \ |
|