Confluence has been migrated and upgraded. Please file an INFRA ticket if you see any issues.
From: Matt Kettler Date: Thu, 10 Jun 2004 12:24:14 -0400
Actually, I suspect you really have the problem backwards.. Rather than avoiding using syslog with SA, you're probably better off configuring syslog to put log messages where you want them.
Pick an unused local facility ie
Configure SA log to that facility by using the -s parameter.
Configure your syslogd to dump
local5.* into a separate file, and exclude it from your other logs. Here's a quick syslog.conf example:
This is the same kind of configuration with syslog-ng which mostly part of the modern systems, separate mail logs from other:
Once you understand how to use syslog properly, you won't have problems like this. After all... syslog IS a pervasive element of unix.You can't avoid it forever. It's better to learn how to use it, rather than trying to figure out how to go around it all the time on a per-program basis.