I have closed the socket after shutting down the socket
(shutdown(sock,2)). Still recvfrom is hanging ( infact
blocking on that socket). I would like to know whether
any one has faced this problem.
Thanks & Regards,
Rajesh.
-----Original Message-----
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>; Andi Kleen <ak@suse.de>; Venkata
Rajesh Velamakanni <rajesh.venkata@wipro.com>; linux-kernel@vger.rutgers.edu
<linux-kernel@vger.rutgers.edu>
Date: Monday, June 26, 2000 6:46 PM
Subject: Re: Query on UDP Sockets on Linux.
>> close on any file handle should send the shutdown flag and wake up all
>> sleepers (and it does in 2.2.16). the sleepers notice shutdown and
>> error out.
>
>I see no evidence of any code in 2.2.16 to do this. I think you are
mistaken.
>
>In fact you are
>
>static struct file_operations socket_file_ops = {
>..
> NULL, /* flush */
>
>
>So nothing is called in the described case that would even allow shutdown
>flags to be set. You are right that the user could call shutdown() then
close
>thus waking the recvmsg - thats a clean approach.
>
>Alan
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.rutgers.edu
>Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/