Messages in this thread | | | Date | Tue, 19 Aug 2003 07:32:49 -0700 | From | Phil Oester <> | Subject | Re: [PATCH] Ratelimit SO_BSDCOMPAT warnings |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |