SO_BSDCOMPAT MESSAGE

[Vahric MUHTARYAN]

Hi Everybody ,

I installed bind 9.3.1 on fedora core 3 and When I start named
it's giving an message like this " dns2 kernel: process `named' is using
obsolete setsockopt SO_BSDCOMPAT " I check mailing list and history but I
couldn't find any information for solve it , also on google. Do you have any
idea why this message anonced by kernel ? one time named are stopped , any
relation with this message ?

Thanks
Best Regards

Vahric MUHTARYAN
Sistem Mühendisi/System Engineer
DorukNet
Tel / Phone : +90 212 326 92 00
Fax : +90 212 227 28 11
E-mail : vahric.m...@doruk.net.tr
http://www.doruk.net.tr
http://www.doruk.net.tr/english.html

Bu e-posta mesajı kişiye özel olup, gizli bilgiler içeriyor olabilir. Eğer
bu e-posta mesajı size yanlışlıkla ulaşmışsa, e-posta mesajını kullanıcıya
hemen geri gönderiniz ve mesaj kutunuzdan siliniz. Bu e-posta mesajı, hiç
bir şekilde, herhangi bir amaç için çoğaltılamaz, yayınlanamaz ve para
karşılığı satılamaz. Yollayıcı, bu e-posta mesajının - virüs koruma
sistemleri ile kontrol ediliyor olsa bile - virüs içermediğini garanti etmez
ve meydana gelebilecek zararlardan doğacak hiçbir sorumluluğu kabul etmez.
The information contained in this message is confidential, intended solely
for the use of the individual or entity to whom it is addressed and may be
protected by professional secrecy. You should not copy, disclose or
distribute this information for any purpose.
If you are not the intended recipient of this message or you receive this
mail in error, you should refrain from making any use of the contents and
from opening any attachment. In that case, please notify the sender
immediately and return the message to the sender, then, delete and destroy
all copies.
This e-mail message has been swept by anti-virus systems for the presence of
computer viruses. In doing so, however, we cannot warrant that virus or
other forms of data corruption may not be present and we do not take any
responsibility in any occurrence.

[Mark Andrews]

> Hi Everybody ,
>
> I installed bind 9.3.1 on fedora core 3 and When I start named
> it's giving an message like this " dns2 kernel: process `named' is using
> obsolete setsockopt SO_BSDCOMPAT " I check mailing list and history but I
> couldn't find any information for solve it , also on google. Do you have any
> idea why this message anonced by kernel ? one time named are stopped , any
> relation with this message ?
>
> Thanks
> Best Regards
>
> Vahric MUHTARYAN
> Sistem Mühendisi/System Engineer
> DorukNet
> Tel / Phone : +90 212 326 92 00
> Fax : +90 212 227 28 11
> E-mail : vahric.m...@doruk.net.tr
> http://www.doruk.net.tr
> http://www.doruk.net.tr/english.html

Complain to the Linux kernel developers. They should remove
the message or the #define.

I suspect that all usage instances are actually protected
with a #ifdef SO_BSDCOMPAT because it is not in early versions
of the kernel.

e.g.

#ifdef SO_BSDCOMPAT
if (type != isc_sockettype_unix &&
setsockopt(sock->fd, SOL_SOCKET, SO_BSDCOMPAT,
(void *)&on, sizeof(on)) < 0) {
isc__strerror(errno, strbuf, sizeof(strbuf));
UNEXPECTED_ERROR(__FILE__, __LINE__,
"setsockopt(%d, SO_BSDCOMPAT) %s: %s",
sock->fd,
isc_msgcat_get(isc_msgcat, ISC_MSGSET_GENERAL,
ISC_MSG_FAILED, "failed"),
strbuf);
/* Press on... */
}
#endif

Do they really expect application developers to try to
workout what kernel version is running to see if they need
to set SO_BSDCOMPAT especially when some kernel versions
need the option turned on?

As to why it was that the Linux kernel developers thought
that making unconnected UDP sockets return errors after
getting a ICMP message would be good. Unfortunately this
is only really useful in the case where a connected UDP
socket could be used (always talking to the same end point).
There is not enough information to do anything with the
error code when you are talking to thousands of different
clients a second.

They then came up with this socket option to restore the
BSD Socket API behaviour (SO_BSDCOMPAT) and not pass the
error information back up the stack.

They then decided to change the default to be the BSD Socket
API behaviour so the setsockopt(SO_BSDCOMPAT) call was no
longer necessary and decided to make the kernel complain
about all such calls but also did not remove the #define for
SO_BSDCOMPAT.

Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_A...@isc.org

[Stefan Puiu]

Mark, just curious, did you complain about this to any of the Linux
developers? Over time I saw you making complaints about various glitches of
that OS/kernel, and was wondering if there's anybody in the Linux camp made
aware of these things.
I doubt it that users would dare bring issues like this one on, say, the
linux-kernel mailing list.

[Danny Mayer]

Mark Andrews wrote:
>>Hi Everybody ,
>>
>> I installed bind 9.3.1 on fedora core 3 and When I start named
>>it's giving an message like this " dns2 kernel: process `named' is using
>>obsolete setsockopt SO_BSDCOMPAT " I check mailing list and history but I
>>couldn't find any information for solve it , also on google. Do you have any
>>idea why this message anonced by kernel ? one time named are stopped , any
>>relation with this message ?
>>
>>Thanks
>>Best Regards
>>
>>Vahric MUHTARYAN
>>Sistem Mühendisi/System Engineer
>>DorukNet
>>Tel / Phone : +90 212 326 92 00
>>Fax : +90 212 227 28 11
>>E-mail : vahric.m...@doruk.net.tr
>>http://www.doruk.net.tr
>>http://www.doruk.net.tr/english.html
>
>

They probably decided to follow Microsoft's example in Windows 2000 and
when they put out a fix for it, instead of fixing the code, the provided
a WSAIoctl() option for programmers to fix themselves Microsoft's broken
code. See Q263823 for the harrowing details.

Danny