--- In "Fred" <> wrote:
>
> --- "naturalwatt" <martin@> wrote:
> > I have the same problem. The kernel seems to hold
> > the socket in use for just about 60 seconds. My
> > process attempts to bind every 10 seconds until it
> > succeeds.
>
> That's probably the smart thing to do. I've got a test process which I
> use to try to find some way to force the bind() but it looks like I'll
> have to try what you did -- though I'll try once a second. }:-}
>
> There doesn't appear to be any ioctl() or fntcl() or sockopt() that's
> responsible for tailoring the timing on when the TCP/IP stack relents
> and "discovers" dead process resources that can be released and granted
> to others.
>
I don't know enough about Linux, but on Solaris it's a kernel parameter
setting, which is
system-wide, not per-process. So you are unlikely to be able to set it via
ioctl.
One version of HP-UX had a bug in that sockets were essentially never released,
so after a
few months, you had hundreds of sockets in FINWAIT2, and the only solution was
a
reboot.
It might be a dynamic kernel setting somewhere, accessible via the /procfs?
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|