Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site genrad.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!bellcore!decvax!genrad!john
From: john@genrad.UUCP (John Nelson)
Newsgroups: net.unix-wizards
Subject: Re: Fifo files on 4.2?
Message-ID: <799@genrad.UUCP>
Date: Fri, 3-May-85 15:54:51 EDT
Article-I.D.: genrad.799
Posted: Fri May  3 15:54:51 1985
Date-Received: Sun, 5-May-85 03:36:35 EDT
References: <2199@usceast.UUCP> <10340@brl-tgr.ARPA> <5370@umcp-cs.UUCP>
Reply-To: john@genrad.UUCP (John Nelson)
Organization: GenRad, Inc., Bolton, Mass.
Lines: 14
Summary: 

>> For another, the 4.2BSD UNIX domain socket code was so buggy that one
>> endangers his system by trying to use it.
>
>Only the SOCK_DGRAM code!  Pipes are SOCK_STREAM socketpairs (well,
>sort of), and only break if you run out of mbufs (but then exit()
>panics if you run out of mbufs, so why worry about the sockets?).

I hate to disallusion anyone, but SOCK_STREAM is as buggy as SOCK_DGRAM.
Whatever you do, DONT USE OUT OF BAND DATA!   It will crash the system.

I also have a program which crashes both ULTRIX and BSD4.2 as distributed:
it calls send and recv on a connected socket pair in SOCK_STREAM.  (Actually,
it calls send and recv with a missing flags argument - nevertheless, it shouldnt
crash the kernel!)