Does MSG_PEEK cause descriptor table problems?

[Chris Torek]

I've been rewriting the parts of the socket stuff dealing with atomic
and connectionless protocols, and discovered this interesting tidbit:
if you receive, in AF_UNIX, with MSG_PEEK, a message containing "rights"
(file descriptors), you get those descriptors then and there.  If you
then receieve without MSG_PEEK, you get them *again*, with apparently
disastrous effect.

Is this not a bug?  How come I haven't seen anything posted about it?

(There are several other bugs in soreceive dealing with MSG_PEEK, too.)
-- 
(This line accidently left nonblank.)

In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris at umcp-cs		ARPA:	chris at maryland