Sockets

[David Arnold]

-->"Aahz" == Aahz Maruch <aahz at netcom.com> writes:
In article <8odh9e$qqf$1 at nnrp1.deja.com>, <karlsass at my-deja.com>
wrote:

  >>  I have a set of spiders running on my system, The spiders
  >> communicate with a urlserver & a processing server via internal
  >> sockets. The spiders are the only ones using Inet sockets. Yet
  >> after a while of say 1 or 2 spiders, a urlserver and process
  >> server running , say for 3 hours, then all of a sudden the system
  >> disallows any connections to the outside, eg inet sockets as well
  >> as Netscape cannot connect to other web located resources.

  Aahz> Yeah, sounds like you're not properly closing down the sockets
  Aahz> after you use them. 

i had a bug yesterday, on WinNT (it was on someone else's system so
i'm not sure about this), where using socket.close() does not close
the underlying socket, byt socket.shutdown() does.

might be worth a go?



d