ipchains packets logs get displayed on active tty (SOLVED)
Hi there!
Sorry to bring up such an old threat, but I didn't see any solutions posted,
and I just found the cause.
The problem was ipchains (or iptables) printing messages on the console no
matter how much you tried to make it shut up :) Well, I had the problem also
with smbmount.
Anyway, the problem was that klogd is displaying on the console all the
messages with any priority greater than debug (7) (see man klogd). To keep
it from doing that, load it with "klogd -c 5" for example. That will log
only errors or highr priorities and will prevent the flooding!
If you use debian, edit /etc/init.d/klogd and edit the line where it says:
KLOGD=""
to be
KLOGD="-c 4"
Have fun!
Miquel
The old message follows:
On Tue, May 01, 2001 at 11:06:52AM +0200, Miquel Mart?n L?pez wrote:
>
> ----- Forwarded message from Lindsay Allen <allen@cleo.murdoch.edu.au> -----
>
> Date: Tue, 24 Apr 2001 07:35:23 +0800 (WST)
> From: Lindsay Allen <allen@cleo.murdoch.edu.au>
> X-X-Sender: <allen@elm.cbcfreo.wa.edu.au>
> To: <debian-user@lists.debian.org>
> Subject: Re: ipchains packets logs get displayed on active tty
>
> On Mon, 23 Apr 2001, Henrique M Holschuh wrote:
>
> > On Mon, 23 Apr 2001, Lindsay Allen wrote:
> > > All that has been done when I shut down to install a tape drive. (And a
> > > new kernel, of course.) Some time back I had three daemons writing to the
> > > screen, but now it is just ipchains. I would have submitted a bug, but it
> > > could be syslogd, klogd or ipchains and I don't know how to pick between
> > > them. It's odd that it affects very few users.
> >
> > I suspect restarting syslogd without restarting klogd AFTER syslogd finishes
> > reloading causes this, but I haven't tested. ipchains can't be at fault, it
> > logs to the kernel ringbuffer.
>
> Hey, that might be it after all. I just restarted klogd and I think it's
> ok. The loading order in rc2.d is
> S10 sysklogd
> S11 klogd
> so I assumed that that would be enough to fix it. I'll report to the list
> when I'm sure.
>
> > Updating PAM also causes this kind of crap. I don't know why, though.
>
> I have been playing with pam somewhat, trying to get cucipop to
> authenticate to an NT server, but I'm out of my depth here...
>
> Cheers,
> Lindsay
>
> --
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Lindsay Allen <allen@cleo.murdoch.edu.au> Perth, Western Australia
> voice +61 8 9316 2486, 0403 272 564 32.0125S 115.8445E Debian Linux
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
> ----- End forwarded message -----
Reply to: