You can use SO_REUSEADDR, but you might find that
the process that last bind'ed to the port will hoard
the data. At least this is what I have seen.
You might be better off implementing something where
the 2 client processes register a with a server process which
in turn opens the socket, binds, then subscribes to the
multicast groups.
Hope this helps,
Tuan
On Thu, 6 Apr 2000, Matias Freytes wrote:
> Hello,
> I am experimenting with a multicast application, but I have only
> one PC, so I'll the application on two different xterms. I need these two
> processes to share a port. I've checked with
>
> #ifdef SO_REUSEPORT
> ......
> #endif
>
> and SO_REUSEPORT is not defined (redhat 6, K 2.2.5-15).
> Should I use SO_REUSEADDR istead?
>
> Thank you.
> Matias.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
