[ previous ] [ next ] [ threads ]
 From:  Ron Rosson <ron at oneinsane dot net>
 To:  m0n0wall <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] Syslogd Help
 Date:  Sun, 15 May 2005 17:23:07 -0500
Using FreeBSD.. 

But doesn't that entry you have below cause it to log in /var/log/messages
as well as the log you have defined?


Ron Rosson
ron at oneinsane dot net

> From: Brett Krueger <sigterm at rootednetworks dot com>
> Date: Sun, 15 May 2005 12:12:02 -1000
> Cc: m0n0wall <m0n0wall at lists dot m0n0 dot ch>
> Subject: Re: [m0n0wall] Syslogd Help
> Ron:
> What unix/linux distro are you using to log the files to?
> usually a linux distro's syslog is: syslogd -m 0 -r
> and that will receive syslog events from other servers, etc.
> syslog-ng is good but true, its a pain sometimes to config.
> And you can just put a rule into syslog.conf to catch the incoming
> messages and put them in their own file as well.
> !m0n0wall  /var/log/m0n0.log
> all syslog.conf is , in general is a filter for raw logs to go somewhere.
> -brett
> Ron Rosson wrote:
>> I have been looking into doing this as well but I would like m0n0wall to log
>> to its own files and not the files that the syslog server would be logging
>> for itself. Is this possible without having to replace syslog with
>> syslog-ng.
>> -Ron
>> P.S. For some reason me and syslog-ng never got along when it came to
>> configs.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch