[syslog-ng] ng to ng then to syslog

[Frans Stekelenburg]

I agree with the previous poster, why indeed use another (lesser) syslog
;-)
But if you insist:

Try with the 'spoof_source(yes)' as option in your tcp(... <options>).
I also learned that localip() can be used to force a certain local ip,
but I don't think that applies to your setup.

Ref: 
http://www.balabit.com/products/syslog_ng/reference-2.0/syslog-ng.html/i
ndex.html#destinations

'luck!

Frans


-----Original Message-----
From: Gerardo Amaya [mailto:joseg at galileo.edu] 
Sent: Friday, July 29, 2005 11:10 PM
To: syslog-ng at lists.balabit.hu
Subject: [syslog-ng] ng to ng then to syslog

Hello all. First thanks for all the help on first issue, it was some 
stupid filter.

I'm configured to send syslog messages from server1 to server2 both with

syslog-ng. Now what I need is to pass messages from server1 to server2 
via syslog-ng(already done that) and as soon as the event gets in 
syslog-ng of server2 to send it to syslog daemon in server2. I have also

done that but the problem is that the events appear as they are coming 
locally and not from server1. Is there a way to change that?

thanks in advance

Gerardo Amaya
_______________________________________________
syslog-ng maillist  -  syslog-ng at lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html