BIND SO_BSDCOMPAT warnings
bdubbs at swbell.net
Mon Nov 7 08:19:19 PST 2005
Andrew Benton wrote:
> When the named daemon is running it generates some annoying messages in
> the logs such as
> kernel: process `named' is using obsolete setsockopt SO_BSDCOMPAT
> According to google, the solution is to comment out references to
> SO_BSDCOMPAT in the BIND source. So I knocked up the attached patch
> which seems to work.
Andy, please see if this works instead:
sed -i -e '247a #undef SO_BSDCOMPAT\n' lib/isc/unix/socket.c
I prefer seds where we can because they are more visible to the user.
More information about the blfs-dev