CA beacon socket disconnect message (benign) on windows if no network interface

[Jeff Hill]

If the windows host has no valid network interfaces
we see this message.

..online_notify.c: CA beacon socket disconnect error was "A socket operation wa
s attempted to an unreachable host. "

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

[Jeff Hill (johill-lanl)]

maybe this code in rsrv should not execute if beacon address list is empty? Need to run some more tests.

        {
            /*
          * Connect to INADDR_NONE because a UDP connect to AF_UNSPEC
             * only works with modern IP kernel.
             * INADDR_NONE can never be a source address and therefore no
             * messages can be received.
          */
            osiSockAddr sockAddr;
            memset ( &sockAddr, 0, sizeof ( sockAddr ) );
            sockAddr.ia.sin_family = AF_INET;
            sockAddr.ia.sin_addr.s_addr = INADDR_NONE;
            sockAddr.ia.sin_port = htons ( port );
            status = connect ( sock,
              & sockAddr.sa, sizeof ( sockAddr.sa ) );
            if ( status < 0 ) {
                char sockErrBuf[64];
                epicsSocketConvertErrnoToString ( sockErrBuf, sizeof ( sockErrBuf ) );
                errlogPrintf ( "%s: CA beacon socket disconnect error was "%s"\n",
                    __FILE__, sockErrBuf );
            }
        }

[Jeff Hill (johill-lanl)]

maybe introduced in R3.14.8

[Jeff Hill (johill-lanl)]

caused by the patch for #217

[Jeff Hill (johill-lanl)]

committed a fix

[Andrew Johnson (anj)]

Patch included in R3.14.9.

[Andrew Johnson (anj)]

R3.14.9 Released.