From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ralf Angeli Newsgroups: gmane.emacs.devel Subject: Re: gnus makes emacs lose response Date: Wed, 19 Apr 2006 22:18:47 +0200 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1145477907 20739 80.91.229.2 (19 Apr 2006 20:18:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 19 Apr 2006 20:18:27 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 19 22:18:24 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FWJ7x-0002El-Ky for ged-emacs-devel@m.gmane.org; Wed, 19 Apr 2006 22:18:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FWJ7x-0005oA-1V for ged-emacs-devel@m.gmane.org; Wed, 19 Apr 2006 16:18:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FWJ7l-0005o5-JQ for emacs-devel@gnu.org; Wed, 19 Apr 2006 16:18:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FWJ7i-0005np-HA for emacs-devel@gnu.org; Wed, 19 Apr 2006 16:18:05 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FWJ7i-0005nm-9a for emacs-devel@gnu.org; Wed, 19 Apr 2006 16:18:02 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FWJ8s-0003UK-Vm for emacs-devel@gnu.org; Wed, 19 Apr 2006 16:19:15 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FWJ7N-00026G-A9 for emacs-devel@gnu.org; Wed, 19 Apr 2006 22:17:41 +0200 Original-Received: from dialin-212-144-186-193.pools.arcor-ip.net ([212.144.186.193]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Apr 2006 22:17:41 +0200 Original-Received: from angeli by dialin-212-144-186-193.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Apr 2006 22:17:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 45 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dialin-212-144-186-193.pools.arcor-ip.net Cancel-Lock: sha1:VoeTFjbIeF03KiUM5snyJfO8A40= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:53099 Archived-At: * Ralf Angeli (2006-04-17) writes: >> Lisp Backtrace: >> "accept-process-output" >> "imap-wait-for-tag" >> "nnimap-retrieve-groups" >> "gnus-retrieve-groups" > > Is there anything else I can do to help debugging this? > > I don't have the original report, so I don't know under which > circumstances the hang happens there. In my case it happens if I > connect to the internet via modem, open an encrypted connection to an > IMAP server, cut the internet connection, connect to the internet > again, and try to connect to the IMAP server again. I am not sure if > this is a problem of Emacs, the programs used for opening the > connection to the server, or the kernel. I tried it now with openssl > s_client, starttls, and gnutls-cli. All three behave identically on > GNU/Linux, i.e. the hang happens with all of them. > > BTW, in contrast to Emacs on GNU/Linux, the Windows port of Emacs does > not hang. Perhaps this information helps identifying the cause. After some messing around I found the difference between between both cases. Under Windows the process (e.g. openssl s_client) dies as soon as the modem connection is closed while on GNU/Linux it is kept alive. That means after reconnecting to the internet under Windows a new process is started which has no problem communicating to the server while on GNU/Linux the old one is reused which obviously cannot cope with the new internet connection. I am not sure what the right course of action on GNU/Linux would be to remedy the problem. Should programs like openssl die when the internet connection is being closed? Or renegotiate a connection? Should Emacs kill the respective processes if there is no answer after a certain amount of time and start new ones? I guess the latter suggestion is not sensible because Emacs does not know why there is no answer. It could as well be that the server is down. For now, I think, I can work around this problem by writing a script which closes the internet connection as well as kills all openssl (and similar) processes. -- Ralf