From xemacs-m  Fri Mar 21 15:02:18 1997
Received: from mail.cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.8.55])
	by xemacs.org (8.8.5/8.8.5) with SMTP id PAA06334
	for <xemacs-beta@xemacs.org>; Fri, 21 Mar 1997 15:02:18 -0600 (CST)
Received: from calico.cis.ohio-state.edu (calico.cis.ohio-state.edu [164.107.142.11]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id QAA26976; Fri, 21 Mar 1997 16:02:10 -0500
Received: (ware@localhost) by calico.cis.ohio-state.edu (8.8.0/8.6.4) id QAA09761; Fri, 21 Mar 1997 16:02:09 -0500 (EST)
To: xemacs-beta@xemacs.org
Subject: Re: gnus freezes
References: <87lo7mcp7t.fsf@sbt.net> <rviv2lug3i.fsf@sdnp5.ucsd.edu>
From: Pete Ware <ware@cis.ohio-state.edu>
Date: 21 Mar 1997 16:02:06 -0500
In-Reply-To: David Moore's message of 21 Mar 1997 12:48:01 -0800
Message-ID: <vwmafnxufg1.fsf@calico.cis.ohio-state.edu>
Lines: 15
X-Mailer: Gnus v5.4.30/XEmacs 19.15(beta101)

David Moore <dmoore@ucsd.edu> writes:

> Michael Harnois <mharnois@sbt.net> writes:
> 
> > trying to open it, and I couldn't C-g out of it. However, issuing a
> > kill -INT to the xemacs process unhung it and it continued normally.
> 
> Right, certain system calls like (connect) can not be interrupted by

I thought the user i/o was interrupt driven?  Otherwise, C-g would
never work.  Or is that the interface to connect() disables SIGIO?
Perhaps it needs to be: (1) better at detecting an interrupt from C-g;
(2) better at restarting the connect() when it is interrupted.

--pete

