[syslog-ng] [Bug 187] Syslog-ng truncates SDATA PARAM VALUE to 256 chars

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Tue Jul 24 12:07:18 CEST 2012


--- Comment #3 from Gergely Nagy <algernon at balabit.hu>  2012-07-24 12:07:18 ---
(In reply to comment #2)
> alloca() would not cause serious performance degradation while still keeping the size of the SDATA value dynamic. The stack size 
> is 256k by default, so using a maximum limit of 64k could be realistic.
> Would that be enough in your use-case? Can you please post more details what you'd like to transmit in your SDATA section?

I was thinking whether scratch-buffers could be used in this case? That would have some minor performance impact in corner cases when the buffer needs to grow,
but otherwise it shouldn't, and would allow pretty much infinite length.

I'm not entirely sure scratch-buffers are usable in this case, though. But if they are, they sound like a better approach than alloca() to me.

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list