I've now had v5.3.6 running on my production environemnets since friday with no problems
one side effect of the cleanups is that previously when I had multiple filters write to one file I was getting lots of corrupt lines, but the change to have omfile write each transaction rather than just as the buffer filled up seems to have eliminated this (it went from 10's of thousands of corrupted lines/day to none over the weekend and monday, tonight's report will be the acid test to see if it's fully cleaned up) I realize there is still a window for corruption (if two output threads running at the same time both decide they need to write at the same time), but it seems that in practice it's effectively gone. David Lang On Fri, 15 Jan 2010, [email protected] wrote: > On Fri, 15 Jan 2010, Michael Biebl wrote: > >> BTW, I'm actually surprised that you don't encounter those problems >> yourself. > > I'm running 5.3.5 still, I haven't had time to build a new version (hopefully > tomorrow) > > David Lang > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
