Date: Fri, 9 Apr 1999 13:21:24 +0100 (BST) From: alan@lxorguk.ukuu.org.uk (Alan Cox) To: fygrave@tigerteam.net (CyberPsychotic) Cc: linux-c-programming@tower.itis.com, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org Subject: Re: linux recvfrom differencies Message-ID: <m10VaHk-0007TvC@the-village.bc.nu> In-Reply-To: <Pine.GSO.4.05.9904090907270.9381-100000@kyrnet.kg> from "CyberPsychotic" at Apr 9, 99 09:22:14 am
next in thread | previous in thread | raw e-mail | index | archive | help
> back) linux returns -1 for next recvfrom with herrno(?) set to REFUSED, > while BSD/Solaris just ignore this. > > The question is: > is there any paper/RFC/FYI which puts a standard on such things, or this is > basically `the matter of taste' of OS developers, and thus just should being > watched carefully, while developing multi-platform applications? RFC1122 requires that icmp errors get back to the application. POSIX 1003.1g was written by people who didn't read the RFC. Now that 1003.1g is basically completed we finally have scope for a spec that means something. Linux quite intentionally has #ifdef SO_BSDCOMPAT int one=1; setsockopt(socket_fd, SOL_SOCKET, SO_BSDCOMPAT, &one, sizeof(one)); #endif so you can force the relevant BSDisms. Unfortunately despite repeated requests to the glibc team it appears this is _still_ not being set by glibc when you compile with -D__BSD_SOURCE. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m10VaHk-0007TvC>