Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Configure REUSE ADDRESS MULTIPLE SOCKET 2 ONE PORT

by Anonymous Monk
on Aug 23, 2001 at 02:42 UTC ( [id://107184]=perlquestion: print w/replies, xml ) Need Help??

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

This node falls below the community's threshold of quality. You may see it by logging in.
  • Comment on Configure REUSE ADDRESS MULTIPLE SOCKET 2 ONE PORT

Replies are listed 'Best First'.
Re: Configure REUSE ADDRESS MULTIPLE SOCKET 2 ONE PORT
by kschwab (Vicar) on Aug 23, 2001 at 09:19 UTC
    Yow, your post could use a little formatting.

    In any case SO_REUSEADDR isn't going to help you launch two apps that bind to the same port at the same time (10048 in this case).

    SO_REUSEADDR is only useful when you want to fire up something even though the port is still in a TIME_WAIT state. This isn't permitted normally, as there is a small chance that you could get unexpected data from an old session on the port.

    If you are really determined to try it:

    setsockopt(SOCK, SOL_SOCKET, SO_REUSEADDR,1) || die "setsockopt() failed: $!\n"; -- or from IO::Socket -- $sock = IO::Socket::INET->new( Reuse => 1, ...Other settings here );
    It does sound like you are using a client, and not a server though. Re-read your own excerpt:Client programs usually need not call bind at all
Re: Configure REUSE ADDRESS MULTIPLE SOCKET 2 ONE PORT
by Anonymous Monk on Apr 24, 2007 at 12:16 UTC
    where we need to add this code

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://107184]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (4)
As of 2025-07-11 06:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?
    erzuuliAnonymous Monks are no longer allowed to use Super Search, due to an excessive use of this resource by robots.