in reply to Re (tilly) 1: Socket Differences between Win32/Darwin and *nix.
in thread Socket Differences between Win32/Darwin and *nix.

Excellent articles on this delay after closing a socket on a bound port are linked from here.

OP: Read the FAQ articles (some are linked in the follow-ups) and if you decide that you want to bind on the port again immediately, use setsockopt and monkey with the SO_REUSEADDR option.

  • Comment on Re: Re (tilly) 1: Socket Differences between Win32/Darwin and *nix.

Replies are listed 'Best First'.
(tye)Re: Socket Differences between Win32/Darwin and *nix.
by tye (Sage) on Jan 10, 2002 at 20:34 UTC

    Or simply add Reuse=>1 to your IO::Socket::INET->new call.

    Update: ...which was already in the original code. Which makes me wonder how this particular error could happen...

            - tye (but my friends call me "Tye")