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
--- bind-9.3.1/lib/isc/unix/socket.c~ 2004-11-18 21:31:16.000000000 +0000
+++ bind-9.3.1/lib/isc/unix/socket.c 2005-11-07 13:34:28.000000000 +0000
@@ -1344,7 +1344,7 @@
{
isc_socket_t *sock = NULL;
isc_result_t ret;
-#if defined(USE_CMSG) || defined(SO_BSDCOMPAT)
+#if defined(USE_CMSG)
int on = 1;
#endif
char strbuf[ISC_STRERRORSIZE];
@@ -1429,7 +1429,7 @@
return (ISC_R_UNEXPECTED);
}
-#ifdef SO_BSDCOMPAT
+/* #ifdef SO_BSDCOMPAT
if (setsockopt(sock->fd, SOL_SOCKET, SO_BSDCOMPAT,
(void *)&on, sizeof(on)) < 0) {
isc__strerror(errno, strbuf, sizeof(strbuf));
@@ -1439,9 +1439,9 @@
isc_msgcat_get(isc_msgcat, ISC_MSGSET_GENERAL,
ISC_MSG_FAILED, "failed"),
strbuf);
- /* Press on... */
+
}
-#endif
+#endif */
#if defined(USE_CMSG)
if (type == isc_sockettype_udp) {
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
