From: Phil Oester <kernel@theoesters.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: [PATCH] Ratelimit SO_BSDCOMPAT warnings
Date: Tue, 19 Aug 2003 07:32:49 -0700 [thread overview]
Message-ID: <20030819073249.A26949@ns1.theoesters.com> (raw)
In-Reply-To: <20030819010550.GF11081@mail.jlokier.co.uk>; from jamie@shareable.org on Tue, Aug 19, 2003 at 02:05:50AM +0100
Admittedly, recompiling Bind after commenting out the #define from
asm/socket.h does also solve the errors. But it does seem overkill
to warn on every single use of this...
Phil
On Tue, Aug 19, 2003 at 02:05:50AM +0100, Jamie Lokier wrote:
> Jamie Lokier wrote:
> > David S. Miller wrote:
> > > I see no reason to apply this, just fix your apps and the
> > > warning will stop. There's only a handful of programs
> > > that trigger this at all.
> >
> > Unfortunately Red Hat's BIND is among the more prominent. :-/
>
> Sorry, I didn't mean to imply _just_ Red Hat. Probably all distros'
> BINDs use SO_BSDCOMPAT. What I meant was this is the only program I
> notice the warning from, when running a 2.5 kernel on an otherwise Red
> Hat 9 system. And it comes up every time I connect to the net, when I
> restart named with new forwarders, which is about hourly :/
>
> -- Jamie
next prev parent reply other threads:[~2003-08-19 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 22:06 [PATCH] Ratelimit SO_BSDCOMPAT warnings Phil Oester
2003-08-18 22:15 ` Valdis.Kletnieks
2003-08-18 22:48 ` David S. Miller
2003-08-19 0:36 ` Jamie Lokier
2003-08-19 1:05 ` Jamie Lokier
2003-08-19 14:32 ` Phil Oester [this message]
2003-08-19 0:37 ` James Morris
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=20030819073249.A26949@ns1.theoesters.com \
--to=kernel@theoesters.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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;
as well as URLs for NNTP newsgroup(s).