Hi, as I see some people running into this same issue time after time (as I did myself). Adding the dummy output trick helps, but users have to know the issue. Usually they run into without knowing it and need to search for the solution.
Maybe its a good idea to improve this by create an additional optional parameter at the input source. If the user enables the parameter, a dummy output will be created for the source internally. By describing the parameter in the docs, users can find the solution before running into the problem and. This would wrap the solution and could prevent users running into this issue. How do you think about this? BR, Peter > As you may have noticed, I also plugged an output.dummy directly onto > the input.http source. This is a nice trick to make sure that even > when the source is not used, its data is flushed. Without it, when the > source is not used, it will keep on receiving data, which will make > its internal buffer override, resulting in garbage sound and lots of > log lines.. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
