[syslog-ng] disk based buffering

Scheidler, Balázs balazs.scheidler at balabit.com
Wed Sep 28 12:47:42 CEST 2016

log-qout-size() controls the size of the memory queue that sits next to the
disk buffer, and it defaults to 64 elements. However it shouldn't apply to
reliable disk buffers (e.g. reliable() setting), because in that case
everything touches the disk before syslog-ng would be sending them on.

Obviously reliable(yes) is a lot slower.



On Wed, Sep 28, 2016 at 9:02 AM, Fabien Wernli <wernli at in2p3.fr> wrote:

> On Wed, Sep 28, 2016 at 03:02:19AM +0200, thejaguar at tutanota.de wrote:
> > So with dqtool ( cool) I noticed that actual problem is that syslog-ng
> is not writing to disk queue immediately when a message is generated.  The
> message goes to usual place like var/log/message etc but not in the queue
> where it should because it has not been transmitted to remote host.  Now I
> am thinking there has to be a memory limit before it starts
> flushing/dumping unsent message to disk queue ? I tried mem-buf-size(1)
> and log-fifo-size(1) but none of them works. Is it a static value or is it
> configurable ?
> If I'm not mistaken the message will go to the destination's memory queue
> first; if the latter is full, only then will it make it to the diskq.
> You can check the status of the queue using the control socket
> (syslog-ng-ctl stats)
> ____________________________________________________________
> __________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?
> product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20160928/a1c3d915/attachment.htm 

More information about the syslog-ng mailing list