Hi Though not syslog-ng specific I feel I have to comment: The loghost statement in Solaris isn't a hack, but lost art of mid 1980s BCPs (in the days that BSD was the "real" thing): Each server had the role name attached to the word host. So you got: loghost, mailhost, boothost, localhost (yes, localhost) etc ... In order to exploit the loghost statement in Solaris you need to change the /etc/hosts file on each solaris system because this where the loghost is defined (usually as an alias to localhost) and the name resolving is set to: "file dns" (in /etc/nsswitch.conf). Paolo --- Valdis.Kletnieks@vt.edu wrote:
On Tue, 03 Jan 2006 13:52:46 PST, Bill Nash said:
Each individual device must be configured to send it's traffic to the syslog server. I am unaware of any platform that is capable of automatically determining where it's logging should go, and sending it along accordingly.
For what it's worth, Solaris boxes have an interesting hack, where they basically route a copy of all syslog output to whatever 'loghost' resolves to. So all you do is create a CNAME tha aliases 'loghost.your.domain' to the name of your logserver, and you're done. ;)
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
__________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com