[SpamAssassin Wiki] Updated: SeparateLogFile

[co...@spamassassin.apache.org]

   Date: 2005-02-09T14:22:51
   Editor: JustinMason
   Wiki: SpamAssassin Wiki
   Page: SeparateLogFile
   URL: http://wiki.apache.org/spamassassin/SeparateLogFile

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,30 +1,34 @@
-
 From: Matt Kettler Date: Thu, 10 Jun 2004 12:24:14 -0400
 
+{{{
 At 03:51 AM 6/10/2004, Bo-Lina teknisk support wrote:
 >Is there anny way of getting SA logging into a separate file instead of
 >putting it into syslog?
+}}}
 
 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 local5.
+Pick an unused local facility ie {{{local5}}}.
 
 Configure SA log to that facility by using the -s parameter.
+
+{{{
          spamd -s local5
+}}}
 
-Configure your syslogd to dump local5.* into a separate fie, and exclude it 
-from your other logs.
+Configure your syslogd to dump {{{local5.*}}} into a separate file, and exclude it 
+from your other logs.  Here's a quick syslog.conf example:
 
-here's a quick syslog.conf example:
-         *.info;mail.none;authpriv.none;cron.none;local5.none; 
-/var/log/messages
-         local5.*; 
-/var/log/spamassassin
+{{{
+         *.info;mail.none;authpriv.none;cron.none;local5.none;    /var/log/messages
+         local5.*;         /var/log/spamassassin
+}}}
 
 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.
+