El Miércoles, 18 de Marzo de 2009 11:04, Rainer Gerhards escribió:
> When you are ready, I'd actually suggest that I create an "omoracle" git
> branch for you and do place a copy of ommysql into it. This, together with
> the comments from omtemplate, would probably one way to get a (non-optimal)
> quick start.
>
So, I'm starting it and I already have something that compiles. Next
step is to have something I can test, then have something that makes
something, then something that does the same but fast.
> I would suggest that we build a very basic oracle driver first and after we
> see it works well, then look into the performance optimization.
>
That's my idea, too. I want something that:
1) Connects to the DB at createInstance() time.
2) Runs the un-prepared statement passed as template on each syslog
entry.
3) Disconnects only at freeInstance() time.
Prepared statements and batch operations will be added later, indeed.
But first, I'd like to know what ways I have to test my module, other
than recompiling it, installing and restarting rsyslog for each change.
> Let me know what you think (and when you have time).
I'm already on it. I hope to deliver something for review next week.
Cheers.
--
Luis Fernando Muñoz MejÃas
Luis.Fernando.Munoz.Mejias@cern.ch
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
> When you are ready, I'd actually suggest that I create an "omoracle" git
> branch for you and do place a copy of ommysql into it. This, together with
> the comments from omtemplate, would probably one way to get a (non-optimal)
> quick start.
>
So, I'm starting it and I already have something that compiles. Next
step is to have something I can test, then have something that makes
something, then something that does the same but fast.
> I would suggest that we build a very basic oracle driver first and after we
> see it works well, then look into the performance optimization.
>
That's my idea, too. I want something that:
1) Connects to the DB at createInstance() time.
2) Runs the un-prepared statement passed as template on each syslog
entry.
3) Disconnects only at freeInstance() time.
Prepared statements and batch operations will be added later, indeed.
But first, I'd like to know what ways I have to test my module, other
than recompiling it, installing and restarting rsyslog for each change.
> Let me know what you think (and when you have time).
I'm already on it. I hope to deliver something for review next week.
Cheers.
--
Luis Fernando Muñoz MejÃas
Luis.Fernando.Munoz.Mejias@cern.ch
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com