Article View: comp.sys.sun
Article #13731Socket select() broken in SunOS?
From: Chris Johnson
Date: Fri, 09 Feb 1990 17:50
Date: Fri, 09 Feb 1990 17:50
17 lines
1224 bytes
1224 bytes
I was trying to do a little synchronous multiplexing of some stream sockets under SunOS 3.5 using the select() command. From the manual pages and the Berkeley IPC documents, it seemed obvious that select() would only return an indication that a particular socket was ready to be read when I could actually do a successful read() from it. Instead, select() seems to return sockets that cause my read() to block, because they are empty (their internal TPC state is marked as established). Is SunOS broken, or is this how it is supposed to work? What happens on a real Berkeley 4.2 or 4.3 system? Thanks. Chris Johnson DOMAIN: chris@c2s.mn.org Com Squared Systems, Inc. ATT: +1 612 452 9522 Mendota Heights, MN USA FAX: +1 612 452 3607
Technical Details
Message-ID:
<4888@brazos.Rice.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-requestShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request From: chris@com2serv.c2s.mn.org (Chris Johnson) Newsgroups: comp.sys.sun Subject: Socket select() broken in SunOS? Keywords: SunOS Message-ID: <4888@brazos.Rice.edu> Date: 9 Feb 90 17:50:24 GMT Sender: root@rice.edu Organization: Sun-Spots Lines: 17 Approved: Sun-Spots@rice.edu X-Sun-Spots-Digest: Volume 9, Issue 36, message 13