Hi all, I'm working on a client-server whit posix.
I use setsockopt(...,...., SO_RCVTIMEO,....) ; and for process  works
but at thread level doesn't work. Someone can tell me why?
thanks

[ Post a follow-up to this message ]

gio wrote:
> Hi all, I'm working on a client-server whit posix.
> I use setsockopt(...,...., SO_RCVTIMEO,....) ; and for process  works
> but at thread level doesn't work.

Do you set this option for each and every socket you'd like to timeout?

> Someone can tell me why?

It could be because socket options apply to that particular socket
which you specify as the first argument in setsockopt() call. Rather
than to a process or a thread.

[ Post a follow-up to this message ]

Not all "unixes" fully support SO_RCVTIMEO.  Some may have that
defined, but it may be a noop.

If you want to make sure that one does not block waiting for data on a
socket, the much more portable way to go is to use either select() or
poll() and a non-blocking socket.

rick jones
--
The glass is neither half-empty nor half-full. The glass has a leak.
The real question is "Can it be patched?"
these opinions are mine, all mine; HP might not want them anyway... 
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

[ Post a follow-up to this message ]