Problem with socketpair , AF_UNIX and select call - can anybody through any light on this!
strange at nsk.no-ip.org
Fri Oct 12 10:16:36 UTC 2007
On Fri, Oct 12, 2007 at 10:52:01AM +0100, Howard Wilkinson wrote:
> Stephen Croll wrote:
> > Howard Wilkinson wrote:
> >> Can you suggest such a list - I can only find lists for POSIX threads!
> > comp.unix.programmer
> Thanks for that!
> >> Code goes as follows
> > I haven't really looked at the code, except for making mods to get it to
> > compile, but it works for me:
> > pika.localdomain:~/tmp 0:12> uname -a
> > Linux pika.localdomain 22.214.171.124-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007
> > x86_64 x86_64 x86_64 GNU/Linux
> > --
> > Steve Croll
> I obviously oversimplified the code - attached is my real test case .....
> server - Socket is ready to write
> server - Socket is not ready to read
> master - Socket is ready to write
> master - Socket is ready to read
> master - recv - Resource temporarily unavailable(11)
Is there a reason for using SOCK_DGRAM instead of the usual SOCK_STREAM?
The latter will make the recv return 0, indicating the other end closed
the connection, as it did happen, as one peers exits before the other
server - Socket is ready to write
server - Socket is not ready to read
master - Socket is ready to write
master - Socket is ready to read
master - recv - Resource temporarily unavailable(11)
This could be a bug, or standard behaviour for disconnected datagram
sockets (I don't know enough of the standards).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20071012/8cf0f2bb/attachment-0001.bin
More information about the users