Sorry for the delay, it is currently quite busy here at my end :( I have now created a very rough skeleton template output module. You need to pull from git. It is contained in the master branch.
So far, it does not perform useful work. I was a bit hesitant to add much more description, because I think this can either be brief and not matching what you need - or very elaborate (bbok-like), for what I currently do not have enough time. I suggest that you have a look at the template module, and then we simply try to get this going. It would be good if you could ask questions or tell me what needs to be placed inside the module. Or I can create yet another skeleton, based on ommysql, that has a bit more logic so that you can fill in the initial Oracle functionality. That will not offer superior performance, but I think it would be a good starting point to pursue the rest of this project. Please let me know what you think. Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: Tuesday, March 03, 2009 3:26 PM > To: rsyslog-users > Subject: Re: [rsyslog] Documentation on writing rsyslog modules? > > Just one quick note, more following: > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Luis Fernando Muñoz Mejías > > Sent: Tuesday, March 03, 2009 3:29 PM > > To: [email protected] > > Subject: Re: [rsyslog] Documentation on writing rsyslog modules? > > > > Hi there. > > > > > > As I said, I need **excellent** performance. I definitely need > > batch > > > > operations, the ability to prepare the statements given as > > arguments > > > > on the configuration file, and not to commit entries one by one, > > but > > > > after a number of entries are ready or (better) after some not so > > > > small time. According to the advise I got from experts around > here, > > > > I'll have to use Oracle Call Interface for this module, I don't > > know > > > > if there are any licensing issues. > > > > > > I can't comment on the licensing issue, I simply don't know what > > > Oracle demands. > > > > I'm not sure how GPL-compatible it is to link to already existing > > proprietary code. Anyways, first I code, then we test, then we (you, > > actually) decide the legal aspects. > > Actually, not me ;) I leave this risk to the user. If someone pays the > legal counselor, I'll add his POV to the project doc. > > Rainer > _______________________________________________ > 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
