Re: remote syslog question
From: Craig Cowen (craig@allmaui.com)
Date: 06/14/01
- Next message: Karsten W. Rohrbach: "Re: Compiling untrusted source -- what are the risks?"
- Previous message: Yonatan Bokovza: "RE: apache security question"
- In reply to: Peter Pentchev: "Re: remote syslog question"
- Next in thread: Gerhard Sittig: "Re: remote syslog question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 14 Jun 2001 11:46:08 -0700 From: Craig Cowen <craig@allmaui.com> To: Peter Pentchev <roam@orbitel.bg>
Sorry, maybe I misunderstood the question.
Just trying to help.
Peter Pentchev wrote:
> On Thu, Jun 14, 2001 at 10:20:04AM -0700, Craig Cowen wrote:
> > we simply have two lines for each facility.
> > One for remote logging and one for local logging.
> > local*.* has nothing to do with local logging.
> > It is an available facility for programs such as sudo which by default
> > uses local2.*.
>
> And maybe the original poster has configured ipfilter to log
> to local0.something..
>
> G'luck,
> Peter
>
> --
> I've heard that this sentence is a rumor.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: Karsten W. Rohrbach: "Re: Compiling untrusted source -- what are the risks?"
- Previous message: Yonatan Bokovza: "RE: apache security question"
- In reply to: Peter Pentchev: "Re: remote syslog question"
- Next in thread: Gerhard Sittig: "Re: remote syslog question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]