I see where LiS makes no attempt to awaken a read/getmsg/ioctl upon close.
Any idea what the correct semantics are for close vs read/write/ioctl/getmsg/putmsg?
Does close wait until the other operations complete? or does close cause the other operations to abort?
The close causes the other operations to abort.
On Solaris, the same code works fine. i.e. The getmsg fails when another thread closes the file descriptor which getmsg is waiting on.
--
David Lehmann Ulticom, Inc. AOL/Yahoo IM: davidULCM 1020 Briggs Road 1-856-787-2729 Mt. Laurel, NJ 08054 USA
_______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
