jjs <jjs@tmsusa.com> wrote:
>
> 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
> <...>
>
The changelog has:
# --------------------------------------------
# 03/03/08 jmorris@intercode.com.au 1.1083
# [NET]: Nuke SO_BSDCOMPAT.
# --------------------------------------------
Maybe James can tell us what is going on here.
We should at least place a cap on the number of times that message
is printed.
-
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/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:32 EST