DEBUG logs too much ?

Joseph Erlewein jerlewein@mhc.net
Thu, 17 Jan 2002 08:41:55 -0500


This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_154862D3.F998E8A5
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Me too. Never patched a kernel before, so it was exciting. Compiled lots. =
Never patched tho.
Pretty painless.

Anyway, the reason I did it was that I updated my 7.2 installation with =
the latest kernel.
I noticed that under 7.1, the iptables 1.2.3 log directive --log-level =
info caused a problem.

A friend and I looked at changelog and saw that 1.2.5 might resolve this, =
and it did.
Plus I learned a few things. Worth it right there.=20

Anyway, I am not seeing any more logs than I did before the distro change, =
kernel upgrade, and patch up to 1.2.5.=20
What -j LOG lines are you using in your script?
can you provide examples of what you saw before and what you're seeing =
now?

-jre



Joseph R. Erlewein
Information Center Specialist
Munson Healthcare
jerlewein@mhc.net

>>> Nick <nicholas@3wsi.net> 17.Jan.2002 04.14.24 >>>
I sucessfully patched the kernel with iptables-1.2.5 ( YAY ! )
but there's a lot of logs it produced now, kinda hard to see which one is =
my=20
customized and which one it produced by itself.

It's never occured when I use standard iptables from kernel-modules (=20
iptables-1.2.4, debian woody ) unless i stated -j LOG explicitly in the=20
firewall script.

I assumed that maybe I turn on the "Network Packet Filtering Debuging"=20
options in my "make config" in kernel recompiling, so I went back there =
and=20
try make menuconfig again using the ".config" i've created before, but =
turned=20
out that it is NOT selected ...

Any other options I might be overlook ?

Thank you.

--=_154862D3.F998E8A5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV><FONT size=3D1>Me too. Never patched a kernel before, so it was =
exciting.=20
Compiled lots. Never patched tho.</FONT></DIV>
<DIV><FONT size=3D1>Pretty painless.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D1>Anyway, the reason I did it was that I updated my =
7.2=20
installation with the latest kernel.</FONT><FONT size=3D1></FONT></DIV>
<DIV><FONT size=3D1>I noticed that under 7.1, the&nbsp;iptables 1.2.3 =
log=20
directive --log-level info caused a problem.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D1>A friend and I looked at changelog and saw that 1.2.5 =
might=20
resolve this, and it did.</FONT></DIV>
<DIV>Plus I learned a few things. Worth it&nbsp;right there.&nbsp;<BR></DIV=
>
<DIV>Anyway, I am not seeing any more logs than I did before the distro =
change,=20
kernel upgrade, and patch up to 1.2.5. </DIV>
<DIV>What -j LOG lines are you using in your script?</DIV>
<DIV>can you provide examples of what you saw before and what you're =
seeing=20
now?</DIV>
<DIV>&nbsp;</DIV>
<DIV>-jre</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Joseph R. Erlewein<BR>Information Center Specialist<BR>Munson=20
Healthcare<BR><A href=3D"mailto:jerlewein@mhc.net">jerlewein@mhc.net</A></D=
IV>
<DIV><BR>&gt;&gt;&gt; Nick &lt;nicholas@3wsi.net&gt; 17.Jan.2002 =
04.14.24=20
&gt;&gt;&gt;<BR>I sucessfully patched the kernel with iptables-1.2.5 ( YAY =
!=20
)<BR>but there's a lot of logs it produced now, kinda hard to see which =
one is=20
my <BR>customized and which one it produced by itself.<BR><BR>It's never =
occured=20
when I use standard iptables from kernel-modules ( <BR>iptables-1.2.4, =
debian=20
woody ) unless i stated -j LOG explicitly in the <BR>firewall script.<BR><B=
R>I=20
assumed that maybe I turn on the "Network Packet Filtering Debuging" =
<BR>options=20
in my "make config" in kernel recompiling, so I went back there and =
<BR>try make=20
menuconfig again using the ".config" i've created before, but turned =
<BR>out=20
that it is NOT selected ...<BR><BR>Any other options I might be overlook=20=

?<BR><BR>Thank you.<BR><BR></DIV></BODY></HTML>

--=_154862D3.F998E8A5--