Hi,
Fred <> [20080515 16:45:31 -0000]:
>
> --- "mikeciaraldi" <> wrote:
> > --- Bob Lees <bob@> wrote:
> >> If you google for this you will find this problem
> >> has been well exercised in the past, not on this
> >> list but on lists in general. It is a "feature"
> >> of the way the TCP/IP stack works and unfortunately
> >> there is no magic bullet!
> > It is designed to prevent any packets which are
> > already in transit when the port gets closed from
> > causing problems.
>
> It's a shame that there doesn't appear to be a standard, built-in way
> to configure the time that the obsolete resource can be fully
> released. As it is, checking every 10 seconds until one can bind --
> with a one minute abort-because-it-just-won't-come backup -- seems like
> the best solution.
>
Is the original now dead process still in the process list ('ps axf') just in
a semi-zombied state? If you put in some SIG handlers they might be
preventing your application exiting so that port is actually open and
assigned to a real (but unresponsive) task.
What does 'netstat -lnp' show?
Silly question, but you are using REUSEADDR on the original bind() call too?
To be honest you might be better off asking this on a networking coding
mailing list or newsgroup.
Cheers
Alex
--
________________________________
/ Curiosity killed the cat, but \
\ satisfaction brought her back. /
--------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
------------------------------------
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/
|