Depending on what you are using to log on the client, you can use the existing syslogd or syslog-ng for your client. I do a little of both. You can do a man of syslogd and syslogd.conf and that will give you pretty much all the format for the file and the way it works. Basically to forward logging to a loghost you just do something like: local0.info @loghost.mydomain.com That will send facility local0, level info messages to the loghost. And you do similar things for the other facilities you want to forward. For syslog-ng you just set up a destination with a hostname: destination d_loghost {host("loghost.mydomain.com"); }; then your log statement: log { source(src); filter(f_local0); filter(f_info); destination(d_loghost); }; Hope that helps. Drew
-----Original Message----- From: dwarf@solarisresources.com [SMTP:dwarf@solarisresources.com] Sent: Wednesday, October 11, 2000 1:36 AM To: bazsil@balabit.hu Cc: syslog-ng@lists.balabit.hu Subject: [syslog-ng]syslog-ng and Solaris
Hi There,
I've managed to compile up syslog-ng on a Solaris 8 box and have a few questions I hope you can answer:
1. I assume that I can kill the script that starts Solaris Syslogd with no ill effects?
2. Can I set a startup script that runs syslog-ng as a daemon process.
3. I've got most of the options setup the way that I want them but can't seem to figure out how to setup one or two machines as syslog servers and a few dozen machines to forward all syslog messages to both of the syslog servers.
If you could pass along info on the above, that would be greatly appreciated.
thanks in advance, alan
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng