on cygwin, epicsSocketEnablePortUseForDatagramFanout: unable to set SO_REUSEADDR?

Bug #541334 reported by Jeff Hill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
Wishlist
Jeff Hill

Bug Description

This is cygwin feature - a situation where cygwin doesnt behave like posix. On posix we have the attached. To fix this someone will need to add an implementation of epicsSocketEnableAddressUseForDatagramFanout for cygwin that behaves like win32, or just use the native port its much more efficient.

/*
 * SO_REUSEPORT is not in POSIX
 */
epicsShareFunc void epicsShareAPI
    epicsSocketEnableAddressUseForDatagramFanout ( SOCKET s )
{
    int yes = true;
    int status;
    status = setsockopt ( s, SOL_SOCKET, SO_REUSEADDR,
        (char *) & yes, sizeof ( yes ) );
    if ( status < 0 ) {
        errlogPrintf (
            "epicsSocketEnablePortUseForDatagramFanout: "
            "unable to set SO_REUSEADDR\n");
    }
}

Original Mantis Bug: mantis-304
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=304

Tags: ca 3.14
Revision history for this message
Jeff Hill (johill-lanl) wrote :

The message would be emitted by epicsSocketEnableAddressReuseDuringTimeWaitState not by epicsSocketEnableAddressUseForDatagramFanout on WINSOCK

Revision history for this message
Jeff Hill (johill-lanl) wrote :

fixed in R3.14.10

Revision history for this message
Andrew Johnson (anj) wrote :

R3.14.10 released.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.