On Mon, 20 Apr 2009, Rainer Gerhards wrote: >>> ... especially if you think about the data flow. At this point, it >> may make >>> sense to review the data flow. I have described it here: >>> >>> http://www.rsyslog.com/Article350.phtml
one problem with this diagram (and therefor the explination that goes with it) it that it confuses logical steps with objects with threads. I would suggest redrawing the diagram with boxes to delinate thread boundries (if I understand this correctly, this would mean splitting the pre-processing box up into three, each of which would be in the same 'thread' box as the input module) It is also not as clear as it could be what happens when you don't define action queues. I would suggest a sepeate diagram just showing that situation (if I understand it correctly, you could show the single-queue operation, and then have one of the 'actions' be to queue the item into an action queue for async processing. also show where the message formatting take place (again, including which thread is doing the work). it is esecially unclear what happens where when you have the action queues (is the message formatted before it's put into the action queue, or is the format of a message in the action queue exactly the same as in the main queue?) some of this was covered (to at least some extent) by your comments, but this sort of thing is actually covered better with text. I'm not a powerpoint person, but that sort of slideshow (with the text explination) is ideal for this sort of explination. David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
