Bind Error
MikeDawg
mikedawg at gmail.com
Wed Aug 2 03:53:07 UTC 2006
The stable kernel from kernel.org puts out this message. It is a
matter of having BSD compatiblity compiled into the kernel (or as a
module, and enabling that module). I think the kernel module name is
compat or bsdcompat, or something along those lines (don't have kernel
docs in front of me at the moment).
Thanks
Mike
Mark Andrews wrote:
> > Dear All
> >
> > I have facing with following problem in Fedora core 5
> > how can i solve that?
> > Pls help me
> >
> >
> > `named' is using obsolete setsockopt SO_BSDCOMPAT
>
> Complain to Fedora.
>
> There is no reason for production kernels to ever put out
> messages like this. There is no reason for production C
> libraries to ever put out messages like this.
>
> This sort of message should only be used in pre-release
> OS development where you want to ensure, as a OS developer,
> that you have removed the old system call, library call
> etc.
>
> As a third party developer there is no way we can remove
> the setsockopt() call as some Linux kernels depend upon
> it being made for correct operation.
>
> If the OS developer really does not want SO_BSDCOMPAT
> to be used they should remove the #define. The code
> that uses it is protected by a #ifdef/#endif pair.
>
> Mark
>
> > Thanks
> > TRYm
> >
> >
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list