[syslog-ng]Urgent: Mangled messages in pipe() destinations in versions >1.5.8

[Balazs Scheidler]

On Fri, Jan 03, 2003 at 06:08:10PM +0100, Balazs Scheidler wrote:
> On Fri, Jan 03, 2003 at 03:29:38PM +0100, Andreas Schulze wrote:
> > >>>>Balazs Scheidler wrote:
> > >I'm thinking about the possibility of destination references, would that
> > >solve your problem?
> > 
> > Sorry. I don't understand. I'm not sure, that this solves our problem.
> > Can you explain 'destination references' a little bit, please.
> 
> looking at your above example, destination references will not be a
> solution. I meant something like this:
> 
> destination d_pipe { pipe("/tmp/pipe" template("xxx")); };
> 
> destination d_another { destination("d_pipe"); };
> 
> so the messages sent to d_another would also go to d_pipe.
> 
> I will try to think about your problem a bit. ...
> 
> It is not easy to implement, I'd need to share the destination fd & write
> buffers between multiple, independent destination drivers...
> 
> It was not meant to be working the way you used in earlier versions either,
> the fact it worked was only a coincidence.

Syslog-ng 1.5.26 (libol 0.3.9 to be exact) reverts to message based
buffering for pipes, so it should work for you again.

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1