From owner-freebsd-stable@FreeBSD.ORG  Thu Feb  2 10:20:07 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 38DB116A420
	for <freebsd-stable@freebsd.org>; Thu,  2 Feb 2006 10:20:07 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A13D743D48
	for <freebsd-stable@freebsd.org>; Thu,  2 Feb 2006 10:20:06 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk)
	by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD))
	id 1F4bZJ-000LNZ-Hd; Thu, 02 Feb 2006 10:20:01 +0000
Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim
	4.52 (FreeBSD)) id 1F4bZJ-000KpG-C6; Thu, 02 Feb 2006 10:20:01 +0000
To: yar@comp.chem.msu.su
In-Reply-To: <20060201220701.GA29980@comp.chem.msu.su>
Message-Id: <E1F4bZJ-000KpG-C6@dilbert.firstcallgroup.co.uk>
From: Pete French <petefrench@ticketswitch.com>
Date: Thu, 02 Feb 2006 10:20:01 +0000
Cc: peterjeremy@optushome.com.au, freebsd-stable@freebsd.org, ivoras@fer.hr
Subject: Re: Restartable system call behaviour
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2006 10:20:07 -0000

> To the best of my knowledge, connect() being always interruptable
> is correct and well-known.

Fair enough, that answers my question!

> And my 4.11-STABLE system will interrupt connect() on a signal with
> SA_RESTART set, which disagrees with your observations yet agrees with
> the standard.  Perhaps some logic in your software has changed since
> 4.11 times.

Have been puzzling over this a lot actually, as I definitely didnt get
it on 4.11. The conclusion I've come to is that the networking circumstances
have also changed over time, such that it's now more likely for me to get
a signal during a connect, hence it probably always did behave that way, just
that I never saw it. The change to 5 would be a co-incidence then.

thanks,

-pete.