<br><br><div class="gmail_quote">On Wed, Jul 4, 2012 at 10:54 AM, Gergely Nagy <span dir="ltr"><<a href="mailto:algernon@balabit.hu" target="_blank">algernon@balabit.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Francois Durand <<a href="mailto:fdur559@gmail.com">fdur559@gmail.com</a>> writes:<br>
<br>
> Then I guess I'll have to try 3.4.<br>
<br>
</div>I would suggest 3.3 instead (particularly, git head of it, or 3.3.6<br>
which should be out in a week), 3.4 is at the moment, a development<br>
tree, while the 3.3 branch is stable, and aimed at production use.<br></blockquote><div><br></div><div>ok, thanks for the hint!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
> That may solve another issue I have, that may be related. I have several<br>
> webservers whose logs are transfered and aggregated on one central box in<br>
> the same file. I did not investigate enough to make a full report, but the<br>
> central log file is corrupted (different lines seem to mix!) and it seems<br>
> to me that's related to the previous fact since it seems to happen only to<br>
> files that are reread from the start.<br>
<br>
</div>Do you have a single file destination, to which these logs are routed to<br>
on the central server, or different destinations with the same file set?<br></blockquote><div><br></div><div>Each webserver serves many virtual hosts. Each virtual host has one access.log. So for instance, on server 1, we have s1v1.log for vhost 1 and s1v2.log for vhost 2. On server 2, we have s2v1.log and s2v2.log. Then s1v1.log and s2v1.log are aggregated on the central log box into v1.log, and s1v2.log and s2v2.log into v2.log.</div>
<div><br></div><div><br></div><div><br></div></div>