From owner-freebsd-current@FreeBSD.ORG  Mon Aug 11 10:47:02 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A3C7537B401
	for <current@freebsd.org>; Mon, 11 Aug 2003 10:47:02 -0700 (PDT)
Received: from sana.init-main.com (104.194.138.210.bn.2iij.net
	[210.138.194.104])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 547EC43FAF
	for <current@freebsd.org>; Mon, 11 Aug 2003 10:47:01 -0700 (PDT)
	(envelope-from takawata@init-main.com)
Received: from init-main.com (localhost [127.0.0.1])
	by sana.init-main.com (8.12.9/8.12.9) with ESMTP id h7BHiR8Y006903
	for <current@freebsd.org>; Tue, 12 Aug 2003 02:44:27 +0900 (JST)
	(envelope-from takawata@init-main.com)
Message-Id: <200308111744.h7BHiR8Y006903@sana.init-main.com>
To: current@freebsd.org
Date: Tue, 12 Aug 2003 02:44:27 +0900
From: Takanori Watanabe <takawata@init-main.com>
Subject: emacs21 TCP connection failed after update.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Aug 2003 17:47:02 -0000

Hi, after I updated the system, I try to use navi2ch, a client
for WWW based BBS system written in emacs-lisp, and found
It often failes to connect to the server with EALREADY.

Then I investigate the problem, I found 
the code(open-network-stream function @emacs21.3/src/process.c)
assumes that connection attempt is aborted when  a program 
got any signal during connect(2) is issued and the 
next attempt to connect(2) fails with EALREADY after a
connect(2) is interrupted. 
What shall we do?