Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.apps Subject: Re: issue with tcp sockets on linux Date: Tue, 22 May 2012 14:57:18 +0100 Lines: 11 Message-ID: <87bolguxmp.fsf@sapphire.mobileactivedefense.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net z+PmspsZPpUjfRm1sOAA8wgmsaobCBSiglmYRaojjaqTW6iEC/qqQag/n0yx0VdaI= Cancel-Lock: sha1:AFo5dyrMhfoQZLxEykbrmL0pykM= sha1:wqIC7OOWFv1Eq7NcizIoYEy82EE= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: csiph.com comp.os.linux.development.apps:479 GH writes: > Hi all, I've run my application into an issue with recv() hanging > while the server already exited. recv() is not returning any data or > error. More puzzling is that netstat shows on client side the > connection in ESTABLISHED state while on server side netstat reports > no such connection. Can someone shed some light or share any > experience on this? The usual cause of this phenomenon would be that the server started another program which is still running and inherited the established socket because FD_CLOEXEC wasn't set.