28 Feb
2005
28 Feb
'05
4:08 p.m.
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