[syslog-ng] syslog-ng 3.2.2 OSE takes 100% CPU after source files get truncated.

[Gergely Nagy]

On Sun, 2011-02-06 at 12:09 +0100, Balazs Scheidler wrote: 
> 
> Author: Balazs Scheidler <bazsi at balabit.hu>  2010-11-07 15:03:27
> Committer: Balazs Scheidler <bazsi at balabit.hu>  2010-12-10 16:14:09
> Parent: ee1d0d7f0720c3ded0d2bfaf22ca6e42d669b7a6 (separate directory hierarchy into lib/, modules/ and syslog-ng/)
> Child:  26b70812cae04179c939dc8b1f323a24692a30f5 (Performance improvement: file write uses writev instead of per-message write() to write larger chunks)
> Branches: many (24)
> Follows: v3.2.1
> Precedes: 
> 
>     LogProto: apply_state shouldn't allow file offsets over the end-of-file
>     
>     Assume that the file was truncated in this case.
> 
> It is probably present in 3.3 only. Can you check if backporting that
> patch fixes the spinning too?

Checked, 3.3 does not spin, nor does 3.2 with the above patch applied.
Backport for 3.2 is available from the integration/apply_state-fix
branch of my syslog-ng-3.2 tree at:

git://git.madhouse-project.org/syslog-ng/syslog-ng-3.2.git

-- 
|8]