Path: utzoo!attcan!uunet!husc6!cmcl2!brl-adm!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: 4.2 vs 4.3 select() (ARRRRGH!)
Message-ID: <11937@mimsy.UUCP>
Date: 13 Jun 88 11:00:24 GMT
References: <9646@g.ms.uky.edu> <9649@g.ms.uky.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 20

In article <9649@g.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes:
>I just tried out the select code that didn't work on 4.2 and
>guess what? It works fine on a 4.3 system. ARRRGGGH! Why in the
>hell did they distribute something that doesn't work as documented?

Because their funding contract said `thou shalt release by September'.
(Or whatever date it was.  Anyway, as I understand it, the release
date hit, nothing was really ready, so they shipped anyway.  There
were some fixes quitely applied to later tapes.)

>Now that I'm multiplexing, just getting a [SIGURG] signal [for out
>of band data] isn't good enough, cause the program has to be able to
>figure out who sent the thing. ... Does anyone know of a sneaky way
>to make this work on 4.2?

Do a receive for MSG_OOB anyway.  If there is none, it ought to fail
with EWOULDBLOCK, or perhaps return 0.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris