From: N N Ashok <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CONFIG_NETFILTER_DEBUG messages go where?
Date: Sun, 13 Apr 2003 07:17:55 +0000 [thread overview]
Message-ID: <marc-lartc-105021844532081@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105012964618933@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 12 April 2003 02:39, Russell Senior scrawled:
> In my attempt to figure out what is going haywire, I compiled the
> NETFILTER debugging into a kernel and booted it, but I haven't been
> able to figure out where the messages go! I am not seeing anything in
> /var/log/kern.log. Hints anyone?
How about /var/log/message? My syslog.conf is set to log *.info (which I
suspect NETFILTER debug to be using) messages in /var/log/messages.
Ashok
- --
- -----------------------------------------------------------------------------
My public key:
gpg --recv-keys --keyserver blackhole.pca.dfn.de DCB44F2E
http://pgp.mit.edu:11371/pks/lookup?search=N+N+Ashok+%28CSE+MSU%29+%3Cnnashok%40yahoo.com%3E&op=index
[Fingerprint: 4D6D B9F3 D2B6 A22A F4E5 5763 4615 E956 DCB4 4F2E ]
- -----------------------------------------------------------------------------
"...there is nothing so unnatural as the commonplace."
Sir Arthur Conan Doyle in "Adventures of Sherlock Holmes: A Case of Identity"
- -----------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+mQ8jRhXpVty0Ty4RAjYjAKDREmUc3UzrRrM3xoIS69+TjNDrPgCeIEpB
M8UxOmYA92sY26KEyoS2d/M=Y24t
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-13 7:17 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 [this message]
2003-04-13 7:42 ` Russell Senior
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-105021844532081@msgid-missing \
--to=nalkunda@cse.msu.edu \
--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.