[prev in list] [next in list] [prev in thread] [next in thread] 

List:       syslog-ng
Subject:    Re: [syslog-ng]Logs lost in the FIFO
From:       Balazs Scheidler <bazsi () balabit ! hu>
Date:       2005-02-28 16:08:24
Message-ID: 1109606905.4529.66.camel () bzorp ! balabit
[Download RAW message or body]

On Mon, 2005-02-28 at 09:27 -0500, Jay Guerette wrote:
> How exactly does that work? You can only "stop writing" for so long,
> before a buffer fills up and you have to drop messages...

Simple: syslog-ng stops reading. if you have flow-controlled sources
(e.g. unix-stream, or TCP with the other end doing flow control as well)
then at the end the application will block on sending the message.

> 
> On Mon, 28 Feb 2005 09:53:16 +0100, Balazs Scheidler <bazsi@balabit.hu> wrote:
> > On Mon, 2005-02-28 at 01:14 -0500, Jay Guerette wrote:
> > > They're dropped, lost, unrecoverable. There really is nothing else
> > > syslog-ng could do in those situations.
> > >
-- 
Bazsi


_______________________________________________
syslog-ng maillist  -  syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

[prev in list] [next in list] [prev in thread] [next in thread]