All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Senior <seniorr@aracnet.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CONFIG_NETFILTER_DEBUG messages go where?
Date: Sun, 13 Apr 2003 07:42:48 +0000	[thread overview]
Message-ID: <marc-lartc-105021988632641@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105012964618933@msgid-missing>

>>>>> "N" = N N Ashok <nalkunda@cse.msu.edu> writes:

Russell> In my attempt to figure out what is going haywire, I compiled
Russell> the NETFILTER debugging into a kernel and booted it, but I
Russell> haven't been able to figure out where the messages go!  I am
Russell> not seeing anything in /var/log/kern.log.  Hints anyone?

N> How about /var/log/message? My syslog.conf is set to log *.info
N> (which I suspect NETFILTER debug to be using) messages in
N> /var/log/messages.

Nope.  I've got two that I would think would catch them:

  kern.*                          -/var/log/kern.log
  kern.debug                      -/var/log/kern.debug

but nothing related is showing up.  

A chronological sorting "ls -lart" in /var/log shows what is
relatively active and none of those is showing anything recognizable
as netfilter debugging.

Is there a /proc/sys/<mumble> switch I need to turn on?

-- 
Russell Senior         ``I've seen every kind of critter God ever made,
seniorr@aracnet.com      and I ain't never seen a meaner, lower, more
                         stinkin' yellow hypocrite than you!'' 
                                        -- Burl Ives as Rufus Hennessy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-04-13  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12  6:39 [LARTC] CONFIG_NETFILTER_DEBUG messages go where? Russell Senior
2003-04-13  7:17 ` N N Ashok
2003-04-13  7:42 ` Russell Senior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-105021988632641@msgid-missing \
    --to=seniorr@aracnet.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.