linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [FLAME]: Log and console pollution: ip_tables: (C) 2000-2002 Netfilter core team
Date: Tue, 29 Apr 2003 21:12:38 +0200	[thread overview]
Message-ID: <20030429191238.GF990@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <200304300136.30478.mflt1@micrologica.com.hk>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On Wed, Apr 30, 2003 at 01:36:30AM +0800, Michael Frank wrote:
> Hi All,
> 
> I notice anoying messages in logs and on the console such as the above.
> 
> Gladly, most humble authors refrain from this bloat.

Well, it is not any more bloat than printing a line like 'ip_tables:
initialized ip_tables core successfully'.

> Could one ban these messages from the console altogether and perhaps
> mandate sending credits to a seperate "credits log" file

I remember a huge discussion on this subject quite some time (years?)
ago on lkml, so don't let's repeat a flame war about this.

> Regards
> Michael Frank

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      parent reply	other threads:[~2003-04-29 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 17:36 [FLAME]: Log and console pollution: ip_tables: (C) 2000-2002 Netfilter core team Michael Frank
2003-04-29 18:24 ` Maciej Soltysiak
2003-04-29 19:12 ` Harald Welte [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=20030429191238.GF990@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mflt1@micrologica.com.hk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).