From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: jjs@tmsusa.com, linux-kernel@vger.kernel.org
Subject: Re: named vs 2.5.64-mm5
Date: Wed, 12 Mar 2003 20:19:16 +0100 [thread overview]
Message-ID: <20030312191916.20499.qmail@linuxmail.org> (raw)
----- Original Message -----
From: jjs <jjs@tmsusa.com>
Date: Wed, 12 Mar 2003 10:29:12 -0800
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: named vs 2.5.64-mm5
> Greetings -
>
> 2.5.64-mm4 and -mm5 seem more rugged than previous
> kernels, but there are a couple of minor nits - one of them
> is the tendency of named (which appears to work reliably
> under 2.4) to go catatonic under recent 2.5.6x kernels -
>
> More verbose kernel logging may shed some light - or is
> this just a red herring? I get a tons of these in 2.5.64-mm5:
>
> <...>
> process `named' is using obsolete setsockopt SO_BSDCOMPAT
> process `named' is using obsolete setsockopt SO_BSDCOMPAT
> process `named' is using obsolete setsockopt SO_BSDCOMPAT
> <...>
>
> Anybody here running a compliant version of named?
>
> (This is the bind 9.2.1 which ships with Red Hat 8.0)
I would recommend you downloading BIND 9.2.2. It fixes many
bugs. Else, try the latest BIND from RedHat's RawHide repository.
HTH
Felipe
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
next reply other threads:[~2003-03-12 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 19:19 Felipe Alfaro Solana [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:29 named vs 2.5.64-mm5 jjs
2003-03-12 19:31 ` Andrew Morton
2003-03-12 21:16 ` David S. Miller
2003-03-12 22:28 ` jjs
2003-03-12 22:29 ` David S. Miller
2003-03-12 22:31 ` 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=20030312191916.20499.qmail@linuxmail.org \
--to=felipe_alfaro@linuxmail.org \
--cc=jjs@tmsusa.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.