[syslog-ng] Reload does not free up RAM

[Evan Rempel]

We have cases where a syslog-ng buffers quite a bit of data (2GB or so) before
it is able to flush the data to the destination. Currently, the only way to "free up" that RAM
is to restart syslog-ng, which means that some log messages are lost during the restart
window.

I open for discussion the idea that on a reload that syslog-ng flush and free all buffer
space and essentially start from a "just started" state again.

Comments?