Re: EOF being read from open socket?

Replies are listed 'Best First'.
Re^2: EOF being read from open socket? by Elijah (Hermit) on Aug 23, 2006 at 20:45 UTC
That socket has to stay in select because it is still active, connected and needs to be read from and written to.	[reply]
Re^3: EOF being read from open socket? by ikegami (Patriarch) on Aug 23, 2006 at 20:55 UTC
What makes you think it's still connected? What is `sysread` returning? 0? undefined? If undefined, what's in `$!`?	[reply] [d/l] [select]
Re^4: EOF being read from open socket? by Elijah (Hermit) on Aug 23, 2006 at 21:33 UTC
It returns an integer 0 from the sysread function but loads undef into the buffer that sysread stores the data in. I think it is still open because the app never closes it. Maybe I am missing something but this socket is suppose to remain open so I assumed it was since the only one I close is the client socket.	[reply]
Re^5: EOF being read from open socket? by Crackers2 (Parson) on Aug 24, 2006 at 01:48 UTC
Re^6: EOF being read from open socket? by Elijah (Hermit) on Aug 24, 2006 at 12:48 UTC
Some notes below your chosen depth have not been shown here
Re^5: EOF being read from open socket? by ikegami (Patriarch) on Aug 23, 2006 at 21:52 UTC