home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip:5256 comp.unix.wizards:4818
- Path: sparky!uunet!dtix!darwin.sura.net!ukma!kherron
- From: kherron@ms.uky.edu (Kenneth Herron)
- Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards
- Subject: Re: select()/ Bad File Number
- Message-ID: <1992Nov20.172319.4760@ms.uky.edu>
- Date: 20 Nov 92 22:23:19 GMT
- References: <1992Nov19.203621.24788@panther.mot.com>
- Distribution: na
- Organization: University Of Kentucky, Dept. of Math Sciences
- Lines: 20
-
- ronf@panther3.panther.mot.com (Ron Feigen) writes:
-
- >I have a situation where a socket gets closed and instead of select()
- >returning informing me that the socket is ready for reading, I get -1 and errno
- >"Bad File Number".
-
- We have a daemon that does the same thing when it accepts a connection
- and no fds are available (this is dynix so the fd table is small and
- static). As far as I can tell, the client's connect succeeds, and
- the server sometimes acts like the accept() has succeeded (I'm not
- too clear on this part), but any attempt to use the fd from either
- side gives an EBADF. My conclusion is that dynix's network code
- is completely unprepared to deal with this problem :-)
-
- In summary: Check the size of your fd table.
- --
- Kenneth Herron kherron@ms.uky.edu
- University of Kentucky +1 606 257 2975
- Dept. of Mathematics "Your ball goes over them, it sails off the edge into
- a huge cauldren of fire-breathing dragons." "And they call this a par three?"
-