recvfrom() unblocking.. how to do it?

hi experts,
i am trying to unblock the recvfrom(), which is getting blocked coz its
not recieving any data..
i tried to use signal call on SIGHUP but its not working.. plzz help
waiting for u r reply.
Manohar.S

manu <(E-Mail Removed)> wrote:

> i am trying to unblock the recvfrom(), which is getting blocked coz its
> not recieving any data..
> i tried to use signal call on SIGHUP but its not working.. plzz help
> waiting for u r reply.

How about adding a call to select() or poll() with a suitable timeout?


--
No need to believe in either side, or any side. There is no cause.
There's only yourself. The belief is in your own precision. - Jobert
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...

Rick Jones wrote:

> manu <(E-Mail Removed)> wrote:
>
>
>>i am trying to unblock the recvfrom(), which is getting blocked coz its
>>not recieving any data..
>>i tried to use signal call on SIGHUP but its not working.. plzz help
>>waiting for u r reply.
>
>
> How about adding a call to select() or poll() with a suitable timeout?

And don't forget to make the socket non-blocking

--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com

Phil Frisbie, Jr. <(E-Mail Removed)> wrote:
>> How about adding a call to select() or poll() with a suitable timeout?

> And don't forget to make the socket non-blocking

Outside of two or more processes/threads select()ing on the same
socket, is that really necessary? Will select() return the socket as
being readable when it really isn't?

rick jones
--
Process shall set you free from the need for rational thought.
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...

Rick Jones wrote:

> Phil Frisbie, Jr. <(E-Mail Removed)> wrote:
>
>>>How about adding a call to select() or poll() with a suitable timeout?
>
>>And don't forget to make the socket non-blocking
>
> Outside of two or more processes/threads select()ing on the same
> socket, is that really necessary?

For defensive programming it is...

> Will select() return the socket as
> being readable when it really isn't?

Not according to to the Single UNIX Specification Version 3, but there are other
unmentionable OSs that might block.

Also, generally you would loop and read all available data before you blocked on
select() again, so you would need the socket to be non-blocking to look for the
EWOULDBLOCK error.

> rick jones

--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com