[rsyslog] threading - was: output plugin calling interface

[Rainer Gerhards]

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of david at lang.hm
> Sent: Wednesday, May 06, 2009 5:03 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] threading - was: output plugin calling interface
> >
> > Mostly ;) - it is a deep copy of the structure from the main message
queue.
> A
> > deep copy is made because the rule engine may potentially change a
message
> > object (not yet implemented). It copy also helps a lot with the subtle
> issues
> > that occur due to different queue types. Granted, it costs some memory,
but
> > it pays back by greatly reduced complexity (we could do a copy-on-change,
> but
> > that's another larger thing that would needed to be looked at).
> 
> ok, this makes sense (and explains why you don't do single-instance-store,
> so you can ignore that portion of my prior comments)

I had them on my mind ;)

> 
> one other question, how do dynafiles work?
> 
> as I see it (in my probably oversimplified view of things), the output
> module needs to be passed the filename to use for a particular message, 

exactly. Any output can request as many strings as it likes.

Please note that there is much value in that. If you have just the plain
structure, an operator can no longer mangle with the different values,
because this is done during string building.

Rainer

> or
> the output module needs to have access the the messae structure, and the
> dynafile template to do it's own processing.
> 
> David Lang
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com