From: "David S. Miller" <davem@redhat.com>
To: alan@lxorguk.ukuu.org.uk
Cc: davidel@xmailserver.org, linux-kernel@vger.kernel.org
Subject: Re: Obsolete messages ...
Date: Thu, 27 Mar 2003 06:59:11 -0800 (PST) [thread overview]
Message-ID: <20030327.065911.29350824.davem@redhat.com> (raw)
In-Reply-To: <1048776371.2606.60.camel@dhcp22.swansea.linux.org.uk>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: 27 Mar 2003 14:46:11 +0000
In which case they would benefit from net/shut_up sysctl. In lots of
environments they will just be a pain
Keep in mind we have these kinds of messages in 2.4.x right this
very moment, and nobody complains about them nor asks for sysctls
to shut them off.
See net/socket.c:sock_create() for example.
Now, I'll all for netratelimit()'ing the networking ones.
next prev parent reply other threads:[~2003-03-27 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 2:57 Davide Libenzi
2003-03-27 14:21 ` David S. Miller
2003-03-27 14:46 ` Alan Cox
2003-03-27 14:59 ` David S. Miller [this message]
2003-03-27 15:51 ` James Morris
2003-03-27 15:52 ` David S. Miller
2003-03-27 18:11 ` Davide Libenzi
2003-03-27 23:26 ` Dave Jones
2003-03-27 23:44 ` Davide Libenzi
2003-03-28 22:48 ` jjs
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=20030327.065911.29350824.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®