use SIGALRM instead of SIGURG to wakeup blocking socket calls

This commit is contained in:
Jeff Hill
2003-05-01 22:12:44 +00:00
parent 4c5dab8e72
commit 54934b1059
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -702,7 +702,7 @@ void tcpiiu::initiateAbortShutdown ( epicsGuard < callbackMutex > & cbGuard, //
}
}
break;
case esscimqi_socketSigurgRequired:
case esscimqi_socketSigAlarmRequired:
this->recvThread.interruptSocketRecv ();
this->sendThread.interruptSocketSend ();
break;
@@ -18,5 +18,5 @@
enum epicsSocketSystemCallInterruptMechanismQueryInfo
epicsSocketSystemCallInterruptMechanismQuery ()
{
return esscimqi_socketSigurgRequired;
return esscimqi_socketSigAlarmRequired;
}
+1 -1
View File
@@ -176,7 +176,7 @@ epicsShareFunc osiSockAddr epicsShareAPI osiLocalAddr (SOCKET socket);
enum epicsSocketSystemCallInterruptMechanismQueryInfo {
esscimqi_socketCloseRequired,
esscimqi_socketBothShutdownRequired,
esscimqi_socketSigurgRequired,
esscimqi_socketSigAlarmRequired,
esscimqi_shuechanismImplemenedHerein
};
epicsShareFunc enum epicsSocketSystemCallInterruptMechanismQueryInfo