Sorry, this time my reply is sluggish ;) > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Luis Fernando Muñoz Mejías > Sent: Monday, February 16, 2009 11:41 AM > To: [email protected] > Subject: Re: [rsyslog] Documentation on writing rsyslog modules? > > 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. ;)
A test environment is first step to expertise ;) > > > 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. Sounds fair. > > 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%. Sounds good. This is one of the bad things about current code base, though. The formatter should long come from the custom plugin, but I didn't manage to do the script engine so far (the core of custom functions). Not a big deal, but something that annoys *me* ;) > It still needs some real-world testing, > but provided it works, is it interesting for the project? Definitely > If so, should > I submit the patch via bugzilla? Any way is fine. You can also just email me. Proper credits, of course are guaranteed. > Is there any paperwork (copyright > assingmnents a la FSF or whatever) that should be fullfilled? Nope, we think the project is in a strong enough position even if the submitter holds the copyright. Actually, this was one project goal: keep contributions easy. I really don't like all the blabla that e.g. you need to do when contributing to syslog-ng. Just be aware that some parts of rsyslog come under GPL while some come under LGPL (the runtime files). We assume that whatever you contribute comes under the license of the core module. For new runtime files, this means we expect LGPL, else we have a problem license-wise. Really looking forward to your results, Rainer > > Thanks. > -- > Luis Fernando Muñoz Mejías > [email protected] > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
