Closed yiting16 closed 2 years ago
Refer to the POSIX documentation [1] which says that it is "implementation-defined whether the SO_SNDTIMEO/SO_RCVTIMEO option can be set."
[1] https://pubs.opengroup.org/onlinepubs/7908799/xns/setsockopt.html
Proposed fix: https://github.com/aws/aws-iot-device-sdk-embedded-C/pull/1743
The fix is to ignore the error if SO_SNDTIMEO/SO_RCVTIMEO is not supported.
I wonder if there are any side effects of not setting transport send timeouts though.
Refer to the POSIX documentation [1] which says that it is "implementation-defined whether the SO_SNDTIMEO/SO_RCVTIMEO option can be set."
[1] https://pubs.opengroup.org/onlinepubs/7908799/xns/setsockopt.html
Proposed fix: https://github.com/aws/aws-iot-device-sdk-embedded-C/pull/1743
The fix is to ignore the error if SO_SNDTIMEO/SO_RCVTIMEO is not supported.
I wonder if there are any side effects of not setting transport send timeouts though.