On Wed, Oct 21, 2009 at 7:22 AM, Rainer Gerhards <[email protected]>wrote:
> That indeed sounds odd. Are you sure the $ActionFileEnableSync is in front > of > all write statements? On some systems, write statements may be included via > files and if these are in front of the directive, those would be unaffected > by it... > We do also use includes but in this case $ActionFileEnableSync was at the top of the included file with all write statements below it. I will also note that the write volume changed significantly with two different config changes. To uber-simplify my original email: "normal" volume - $ActionFileEnableSync off & all actions include "-" in front : 2-3mbps ~30 iops $ActionFileEnableSync off & all actions exclude "-" in front : 5mbps (~100% increase) (iops unknown) $ActionFileEnableSync on & all actions exclude "-" in front : 9mbps (~300-400% increase) ~900 iops I am using a mix of static and dynamic filename actions and some actions use format templates as well. I suppose there could be one of those combinations which is not honoring the global $ActionFileEnableSync configuration. Again, I need to do some testing because at this point I'm just making guesses without much information. Thanks, Aaron _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
