On Mon, 14 Jan 2002, John Baldwin wrote:
> What are the recommended log settings under the Facilities and Priorities
> sections? Specifically, what should be used for Facilities; local0, local1,
> auth, security, etc.?
Entirely up to you. These are standard syslog facilities to allow you to
log (via syslogd or a functional equivilent) exactly where you want to.
For example, in your /etc/syslog.conf
+hostname.of.gnatbox
local1.* /var/log/my.gnatbox-filter.log
local0.* /var/log/my.gnatbox-nat.log
+hostname.of.second.gnatbox
local1.* /var/log/my.gnatbox2-filter.log
local0.* /var/log/my.gnatbox2-nat.log
#below are from the original freebsd syslog.conf
+@
*.err;kern.debug;auth.notice;mail.crit /dev/console
*.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
security.* /var/log/security
mail.info /var/log/maillog
<snipped>
----
man syslogd and man syslog.conf to find out more. (or the equivilent if
you're using a non-unix based syslogd)
This is just one example that I'm currently using. It's not perfect, but
it did get the logs going...the +@ localhost directive was required in my
case because the gnatbox logs were hitting the wildcard that is directed
to /var/log/messages...and I didnt want them there! :) Some more tuning
on my part will fix this.
You'll also want to man newsyslog.conf to see about rotating your logs at
reasonable times...a busy gnatbox will chew some disk space.
These are just examples...and off the record examples at that. My
disclaimer is that I'm involved with neither support or development, and
havent been using it for very long.
There is a mention on page 91 of the spiral bound manual that mentions and
included windows based logger. I'd guess that all you need to be sure of,
in that case, is that both ends are configured the same..you dont likely
have any conflicting issues to worry about.
good luck.
...david
---
David Raistrick
Systems Administrator - Global Technology Associates, Inc
[EMAIL PROTECTED]
