It appears that the intent of setting a file descriptor to non-blocking mode via pth_fdmode() is to do for the thread what normal non-blocking (without pth involved) does for a process.
Is this the intent? If so, that's great.. but then there are a few bugs in the implementation. While pth_read() and pth_write() have been modified to properly handle the PTH_FDMODE_NONBLOCK case, this still needs to be done for other blocking syscalls, e.g. pth_connect() and pth_accept() to name two. They will block the thread even if the fdmode is PTH_FDMODE_NONBLOCK. I'd really like to see this fixed, and would be willing to supply patches if that would help. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com ______________________________________________________________________ GNU Portable Threads (Pth) http://www.gnu.org/software/pth/ User Support Mailing List [EMAIL PROTECTED] Automated List Manager (Majordomo) [EMAIL PROTECTED]
