Thanks for the confirmation, Botond. BTW, is there a public repository I can use? I have a significant amount of experience with C, and would like to be able to contribute occasional patches (as sparse time allows).
-- Cameron Kerr <cameron.kerr...@gmail.com> See my blog at http://distracted-it.blogspot.co.nz/ (previously http://humbledown.org/) Skype me on cameron.kerr.nz On 19 August 2014 03:02, Botond Botyanszki <b...@nxlog.org> wrote: > Hi, > > On Sat, 16 Aug 2014 02:27:38 +1200 > Cameron Kerr <cameron.kerr...@gmail.com> wrote: > > > Therefore, it seems that the number 260000 is significant (probably the > > size of some buffer), and the bug lies in the management of the buffer > when > > it has reached the end of the buffer, and finds the start of a new > message > > (the rest of which has yet to be written into the buffer). > > The buffer size is 65000 so you are right. I could reproduce the issue by > creating an input file where the line terminator lies at the buffer > boundary. This issue is only present with CRLF when CR is the last byte > in the buffer and LF is read in the next. > > Until a fix is available you could use this workaround: > Exec if size($raw_event) == 0 drop(); > > Thanks for taking the time to chase this. > > Regards, > Botond > > > ------------------------------------------------------------------------------ > _______________________________________________ > nxlog-ce-users mailing list > nxlog-ce-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users >
------------------------------------------------------------------------------
_______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
