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?


-- Dave


At 10:21 AM 10/1/2003 Wednesday, Michael Shimony wrote:
LiS version 2.16.13

When running a program with two threads, one thread is blocked on a call to getmsg, and the other thread closes the file descriptor that getmsg is reading. I would think that this should cause getmsg to return, but instead it just hangs. Has anyone else seen this? Thanks.

Mike

--
Michael Shimony
Senior Software Engineer
Ulticom, Inc., 1020 Briggs Rd., Mt. Laurel, NJ 08054
856-787-2747
http://users.ulticom.com/~shimony



_______________________________________________
Linux-streams mailing list
[EMAIL PROTECTED]
http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams


_______________________________________________
Linux-streams mailing list
[EMAIL PROTECTED]
http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams

Reply via email to