| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
- some cleanup in imklog
- bugfix: potential segfault in imklog when kernel is compiled without
/proc/kallsyms and the file System.map is missing. Thanks to
Andrea Morandi for pointing it out and suggesting a fix.
|
|
|
|
|
|
| |
Thanks to Peter Vrabec for patching it based on the development in
sysklogd - and thanks to the sysklogd project for upgrading klogd to
support the new functionality.
|
|
|
|
| |
varmojfekoj for the patch
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
made this mode the default; this was needed, as some programs (e.g.
sshd) log with inconsistent timezone information, what messes up the
local logs (which by default don't even contain time zone information).
This seems to be consistent with what sysklogd did for the past four
years. Alternate behaviour may be desirable if gateway-like processes
send messages via the local log slot - in this case, it can be enabled
via the $InputUnixListenSocketIgnoreMsgTimestamp and
$SystemLogSocketIgnoreMsgTimestamp config directives
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- moved module loader from conf.c to module.c, where it belongs
- made the necessary plumbing to auto-load library modules
- upgraded debug system to include iRet in function exit message
- changed module interface so that instances need only to be supported by
output plugins (if we actually need them for input plugins, we can
always add it again...)
- milestone: first implementation of library modules (but do not get
unloaded on exit/hup so far)
|
|
|
|
| |
- changed module interface version, as the interface change is quite large
|
| |
|
|
|
|
|
|
|
| |
message submission interface. Part of the ongoing modularization
effort.
- bugfix: invalid kernel log format -- see bug
http://bugzilla.adiscon.com/show_bug.cgi?id=1
|
| |
|
|
|
|
|
|
| |
troubles with the framework, also it was somewhat ugly...)
- fixed a memory leak in object destruction (was recently introduced by
object naming, not present in any released version)
|
|
|
|
|
| |
- restructured code, moved some part out of syslogd.c to action.c, where
they belong (still some more to do in that regard ;))
|
|
|
|
|
|
| |
was specified in rsyslog.conf
- fixed a bug that caused a segfault on queues with types other than "disk"
- removed the now longer needed thread TermSyncTool
|
| |
|
|
|
|
|
| |
- defined a property class
- implemented deserializer (needs some more work)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- implemented $klogSymbolLookup config directive
|
|
|
|
|
|
|
|
|
|
| |
See newsgroup posting for details on the issue:
http://groups.google.com/group/comp.programming.threads/msg/330b9675f17
a1ad6 I tried some mutex operations but came to the conclusion that
this does not really help. So I have now switched to plain thread
cancellation, which so far seems to be OK. Need more practical
experience with other input modules to make a final decision. Thus I
leave all code in and have just disabled the problematic code.
|
| |
|
|
|
|
| |
- implemented $klogSymbolsTwice config directive
|
|
|
|
| |
facility
|
| |
|
| |
|
| |
|
| |
|
|
|