Skip site navigation (1) Skip section navigation (2)

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

From: Alan Cox <alan(at)lxorguk(dot)ukuu(dot)org(dot)uk>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: alan(at)lxorguk(dot)ukuu(dot)org(dot)uk (Alan Cox), kuznet(at)ms2(dot)inr(dot)ac(dot)ru, dyp(at)perchine(dot)com, pgsql-hackers(at)postgresql(dot)org, davem(at)redhat(dot)com (Dave Miller)
Subject: Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection
Date: 2000-07-04 00:05:49
Message-ID: E139GDn-0005te-00@the-village.bc.nu (view raw or flat)
Thread:
Lists: pgsql-hackers 
> No, it doesn't "hang for all eternity", it sits in the same state until
> (a) the client side closes its sending side of the connection (ie, sends
> FIN), or (b) the FIN-WAIT-1 state times out.  But given a normally
> responsive client and no loss of physical connectivity or crash of
> either TCP stack, there is no connection reset and no failure to deliver
> sent data.

I cannot ack the data since it has not been read, so how can I ack the fin ?

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-07-04 00:11:22
Subject: Re: Re: [COMMITTERS] TOAST
Previous:From: Jan WieckDate: 2000-07-03 23:57:07
Subject: Re: Re: [COMMITTERS] TOAST

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group