Rainer, My apologies for the late reply. I was subscribed to the digest format and didn't receive your replies.
> glad you asked :) The documentation is ... well... not much ;) Oops! > The best thing is probably to start with the existing MySQL > module. HOWEVER, I myself would be very interested in a native, > high-performing Oracle driver. I neither have the expertise to do it > not the test environment. I don't have the expertise either, but do have the test environment... we can try. ;) > If you like, we could collaborate on this effort. I'd create a > skeleton output module for you, guide you through using it and you > provide the Oracle bits to it (that should be fairly easy). Of course, > that means your module would need to be contributed back to the > project. That sounds really great. Before you start coding or preparing anything, let me check how well our DBs perform, because it's not yet clear if they'll be able to cope with the high insertion rate we expect. If we don't go for the Oracle database this work doesn't make sense. I bet we'll want the Oracle, anyways. For this evaluation, I already have a timestamp formatter that fits into Oracle, something that can be used with the property replacer, like %timereported:::date-oracle%. It still needs some real-world testing, but provided it works, is it interesting for the project? If so, should I submit the patch via bugzilla? Is there any paperwork (copyright assingmnents a la FSF or whatever) that should be fullfilled? Thanks. -- Luis Fernando Muñoz Mejías [email protected] _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
