[syslog-ng]Full pipe as destination

[Peter Draexler]

Dies ist eine mehrteilige Nachricht im MIME-Format.
--------------077255A7CF900520DB561707
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

We are using syslog-ng on our logserver with multifunctional
logforwarding.
As a special type of destination we are using pipes as a special
interface to commercial applications.

Here is our question:
    What happens with the log events, if the pipe becomes
    temp. unavailable (e.g. the reading end is dead or
    the pipe is full)?

IMHO you have to open() the pipe nonblocking, to avoid your
syslog stucks in-active, in the case one destination is broken.
I think this is true. Correct?

What happens with your internal log buffers, if write() returns -1
and errno set to EAGAIN?
You implement an internal buffering/queue and try to write the
outstanding log events some times later or you simply discard
the buffers as long as one destination is unreachable?

Thanks very much.
Best Regards -- Andreas and Peter

A Hint for syslog-ng.1.5.8 on Solaris 8:
    $DATE in destination templates returns nothing.
    But $FULL|ISODATE works fine.

--
Dr. Peter Dräxler
mediaWays GmbH
Hülshorstweg 30
33415 Verl
Tel. +49-5246-80-1888
Fax  +49-5246-80-2888
peter.draexler@mediaways.net
------------------------------


--------------077255A7CF900520DB561707
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Return-Path: <andreas.schulze@mediaways.net>
Received: from gmws-gtso-de01 ([193.189.241.129])
          by messaging.mediaways.net (Netscape Messaging Server 3.6)
           with SMTP id AAA4000 for <Peter.Draexler@mediaways.net>;
          Mon, 13 Aug 2001 14:52:56 +0200
Received: from mx.mediaways.net ([193.189.224.118]) by gmws-gtso-de01.mediaways.net; Mon, 13 Aug 2001 14:52:44 +0000 (MET)
Delivered-To: @mx.mediaways.net:Peter.Draexler@mediaways.net
Received: (qmail 18884 invoked by uid 4220); 13 Aug 2001 12:52:44 -0000
Received: from unknown (HELO mail.mediaways.net) (193.189.224.113)
  by mx.mediaways.net with SMTP; 13 Aug 2001 12:52:44 -0000
Received: (qmail 18878 invoked by uid 4221); 13 Aug 2001 12:52:43 -0000
Received: from gmws-verl-de01.mediaways.net (HELO gmws-verl-de01) (195.71.226.118)
  by smtp-relay.mediaways.net with SMTP; 13 Aug 2001 12:52:43 -0000
Message-ID: <3AAF77C9.8F33B2B@mediaways.net>
Date: Wed, 14 Mar 2001 14:53:14 +0100
From: Andreas Schulze <andreas.schulze@mediaways.net>
Organization: mediaWays Internet Services GmbH
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: Peter Draexler <Peter.Draexler@mediaways.net>
Subject: Syslog Problematik
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Kannst Du den Balash aus Budapest mal folgendes fragen?

---
We are using syslog-ng on our logserver with multifunctional
logforwarding.
As a special type of destination we are using pipes as a special
interface to commercial applications.

Here is our question:
    What happens with the log events, if the pipe becomes
    temp. unavailable (e.g. the reading end is dead or
    the pipe is full)?

IMHO you have to open() the pipe nonblocking, to avoid your
syslog stucks in-active, in the case one destination is broken.
I think this is true. Correct?

What happens with your internal log buffers, if write() returns -1
and errno set to EAGAIN?
You implement an internal buffering/queue and try to write the
outstanding log events some times later or you simply discard
the buffers as long as one destination is unreachable?

Thanks very much.
Best Regards -- Andreas

A Hint for syslog-ng.1.5.8 on Solaris 8:
    $DATE in destination templates returns nothing.
    But $FULL|ISODATE works fine.
---

Danke -- ASL


--------------077255A7CF900520DB561707--