This is because most applications that use corosync do not test for TIMEOUT but only for TRY_AGAIN. Signed-off-by: Angus Salkeld <asalkeld@xxxxxxxxxx> --- include/corosync/corotypes.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/corosync/corotypes.h b/include/corosync/corotypes.h index 74183d8..c67bf29 100644 --- a/include/corosync/corotypes.h +++ b/include/corosync/corotypes.h @@ -151,6 +151,7 @@ static inline cs_error_t qb_to_cs_error (int result) case ENOMEM: err = CS_ERR_NO_MEMORY; break; + case ETIMEDOUT: case EAGAIN: err = CS_ERR_TRY_AGAIN; break; @@ -158,7 +159,6 @@ static inline cs_error_t qb_to_cs_error (int result) err = CS_ERR_FAILED_OPERATION; break; case ETIME: - case ETIMEDOUT: err = CS_ERR_TIMEOUT; break; case EINVAL: -- 1.7.7.6 _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
