netdev
[Top] [All Lists]

Fwd: Problem with recv syscall on socket when other side closed connecti

To: David S. Miller <davem@xxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx>, Networking Team <netdev@xxxxxxxxxxx>
Subject: Fwd: Problem with recv syscall on socket when other side closed connection
From: Denis Perchine <dyp@xxxxxxxxxxxx>
Date: Mon, 26 Jun 2000 20:40:25 +0700
Sender: owner-netdev@xxxxxxxxxxx
Hello all,

I did not get any answer on this in linux-kernel.
And I send it to maintainers now.
The problem occurs in PostgreSQL 7.0.2.
There's no such problem in FreeBSD & IRIX.
They both gives you 0 after all received data is read.
Any comments?

----------  Forwarded Message  ----------
Subject: Problem with recv syscall on socket when other side closed connection
Date: Sat, 24 Jun 2000 05:58:39 +0700
From: Denis Perchine <dyp@xxxxxxxxxxxxxxx>


Hello all,

There's quite strange behavior of the linux kernel when other side closed 
connection
and we try to read from socket.
Firstly I get -1 and EPIPE in errno. Hmmm... I could not find anywhere in 
standards or manpages
that recv can return EPIPE. OK...
The if I try to continue read I will get the rest of the data which arrived 
between last read and
connection close... Very strange logic... Any comments on this.

-- 
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@xxxxxxxxxxxx
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
-------------------------------------------------------

-- 
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@xxxxxxxxxxxx
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

<Prev in Thread] Current Thread [Next in Thread>