[syslog-ng]odd problem

[Hamilton, Andrew Mr RAYTHEON 5 SIG CMD]

I'm not 100% certain but I don't think that will work.  syslog-ng picks the
first log statement and logs the message to that.  After that it considers
the message logged and will log nothing to the next log statement.  What I
am curious about is why the multiple destination thing didn't work.  I use
it often and it works for me just fine.  I am using 1.4.7 in production but
I have been testing the 1.5 series and will go to production with it soon.
Both seem to do this just fine.  What is the error you are getting from the
multiple destination configuration?

Regards,
Drew

> -----Original Message-----
> From:	Chad C. Walstrom [SMTP:chewie@wookimus.net]
> Sent:	Monday, April 02, 2001 11:19 PM
> To:	syslog-ng@lists.balabit.hu
> Subject:	Re: [syslog-ng]odd problem
> 
> On Mon, Apr 02, 2001 at 04:38:30PM -0400, jon@dumbo.pobox.com wrote:
> > syslog-ng-1.4.11/
> > libol-0.2.21/
> > 
> > i guess i'll try upgrading....
> > 
> > how does one log to multiple destinations without putting everything
> into the same
> > destination XXX {} container?
> > 
> > i've tried seperate destinations
> > ie...
> > destination x { tcp(208.210.124.50 port(514)); }
> > destinayion y {
> file("/var/log/ng/$HOST/$YEAR$MONTH$DAY/$FACILITY.$PRIORITY"
> dir_perm(0755) perm(0644)) }
> > 
> > and then in the log directive 
> > log {
> >     source(src);
> >     destination(x);
> >     destination(y);
> > }
> > 
> > but that gives me errors
> 
> Try:
>     log{ source(src); destination(x); };
>     log{ source(src); destination(y); };
> 
> -- 
> Chad Walstrom <chewie@wookimus.net>                 | a.k.a. ^chewie
> http://www.wookimus.net/                            | s.k.a. gunnarr
> Key fingerprint = B4AB D627 9CBD 687E 7A31  1950 0CC7 0B18 206C 5AFD
>