RE: FW: Question about logging.

From: Erik Paulsen Skålerud (erik_at_pentadon.com)
Date: 05/28/03

  • Next message: Simon L. Nielsen: "Re: FW: Question about logging."
    To: "'Brian Reichert'" <reichert@numachi.com>
    Date: Wed, 28 May 2003 20:04:28 +0200
    
    

    > -----Original Message-----
    > From: Brian Reichert [reichert@numachi.com]
    > Sent: Wednesday, May 28, 2003 7:47 PM
    > Subject: Re: FW: Question about logging.
    > On Wed, May 28, 2003 at 07:41:56PM +0200, Erik Paulsen Skålerud wrote:
    > > I'm forwarding this to security@, as I'm getting no replies
    > on ipfw@.
    > >
    > > Hope it's relevant enough for you :(
    > >
    > > Sorry for asking this, It's probably been asked before, but I've
    > > searched google for a while now with no results :( I'm wondering if
    > > it's possible to restrict ipfw to -only- log to /var/log/ipfw.log ?
    > > Seems like the only way to remove ipfw-logging from the console output
    > > (dmesg) is to disable the security messages to the console.. Is there
    > > really no other way?
    >
    > It says right in the mapagfe for ipfw(8):
    >
    > When a packet matches a rule with the log keyword, a message will
    > be logged to syslogd(8) with a LOG_SECURITY facility.
    >
    > So, unless you modify ipfw iteslf, you get to tune your
    > syslogd.conf file.
    Yeah, I've gotten that far. But, how can I explicity -only- filter out ipfw
    messages from the default console output? Looks like the only way is to
    remove kern.debug :(

    Erik.

    > --
    > Brian 'you ***' Reichert <reichert@numachi.com>
    > 37 Crystal Ave. #303 Daytime number: (603) 434-6842
    > Derry NH 03038-1713 USA BSD
    > admin/developer at large
    >

    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"


  • Next message: Simon L. Nielsen: "Re: FW: Question about logging."
  • Quantcast