delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <f18b7baa0912181333o45e9f070uf589710782b72b5b@mail.gmail.com> |
References: | <f18b7baa0912161805p4cd2ff8cte99b19a95e204440 AT mail DOT gmail DOT com> <772li5l3a44hueai8u9j3g1ccj2rgl06d7 AT 4ax DOT com> <f18b7baa0912171411l7ec900d5kae185dc458ccfd95 AT mail DOT gmail DOT com> <f18b7baa0912181333o45e9f070uf589710782b72b5b AT mail DOT gmail DOT com> |
Date: | Fri, 18 Dec 2009 20:14:44 -0700 |
Message-ID: | <f18b7baa0912181914t47dc3c6cx5610db0c9dfb08b3@mail.gmail.com> |
Subject: | Re: Cygwin 1.7 GNU screen freezing when disconnected |
From: | Karim Ali <khadgar34+cygwin AT gmail DOT com> |
To: | cygwin <cygwin AT cygwin DOT com> |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Fri, Dec 18, 2009 at 2:36 PM, Game Fan wrote: > Wanted to see if cygwin 1.7 is released or not and seen your letter. Don't > need another source of spam so I'm not subscribing to cygwin ML. > Are you sure it's problem with CygWin? I'm seeing such problems quite often > on Linux. The story goes like this: background screen process wants to stop > old foreground process when you are attaching new one to it, but old > foreground process tries to use PTY which lost it's owner! The lock happens > somewhere in kernel so old foreground process can not respond (yes, blocking > API are evil and all that). The solution is simple: find and kill old > foreground process with "kill -9" and connect to screen again. I got this email today off-list. As suggested, killing the program that's running inside screen does make it reattachable, but this doesn't really seem like a real solution to me, since usually I want to see some state that was in screen. Also, I do use Linux sometimes, and the steps I ran doesn't cause screen to freeze there. Thanks, Karim -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |