[syslog-ng]TCP transport reliability

[todd glassey]

Actually what you really want is a synchronous transport bus to carry the
data instead of lowly TCP/IP on top of the flimsy Ethernet. The fix is
probably more likely to be to build in some of the message passing control
features of tools like ISIS or TibCO's TIB Bus.

Todd Glassey

----- Original Message -----
From: "Gregor Binder" <gbinder@sysfive.com>
To: <syslog-ng@lists.balabit.hu>
Sent: Thursday, January 04, 2001 2:51 PM
Subject: Re: [syslog-ng]TCP transport reliability


> SZALAY Attila on Thu, Jan 04, 2001 at 08:58:46PM +0100:
>
> Hi,
>
> > Yes again, and becouse of this, THERE ARE _NO_ SOLUTION for this
problem.
> >
> > If you pour water to a horn in full speed, the water will overflow.
>
> unless of course, the horn has a way to stop the flow of water until
> it has capacity to process some more of it. :)
>
> The only way to solve this problem (IMHO) would be to make i/o to
> syslog-ng a blocking operation. Not many situations where this is
> what you would want.
>
> If your system is not fast enough to process the amount of messages
> that need to go through, and/or doesn't have enough RAM to hold the
> messages until they can go to disk/network, reduce log-traffic or size
> your system accordingly. Slowing down the logging clients hardly can
> be called a solution.
>
> Greetings,
>   Gregor.
>
> --
> Gregor Binder  <gbinder@sysfive.com>  http://www.sysfive.com/~gbinder/
> sysfive.com GmbH             UNIX. Networking. Security. Applications.
> Gaertnerstrasse 125b, 20253 Hamburg, Germany       TEL +49-40-63647482
>
> _______________________________________________
> syslog-ng maillist  -  syslog-ng@lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
>