X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.0 required=5.0 tests=BAYES_40,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
connect():	No such file or directory
From:	Andrew Schulman <schulman DOT andrew AT epamail DOT epa DOT gov>
Subject:	Re: 'screen' started in detached mode -- cannot reattach
Date:	Wed, 28 Apr 2010 12:08:23 -0400
Lines:	35
Message-ID:	<ldmgt5d8o32lj2pknsdp75v7f8itmio2cb@4ax.com>
References:	<1272464872 DOT 10844 DOT ezmlm AT cygwin DOT com> <4BD8543A DOT 9020100 AT gremwell DOT com>
Mime-Version:	1.0
X-Archive:	encrypt
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

> I start 'screen -d -m MYCOMMAND' and it goes into background, as
> intended. However, I cannot reattach to it, the reattaching 'screen'
> process hangs. It is easy to reproduce:
> 
> sh-3.2# screen -d -m sleep 1000
> 
> sh-3.2# screen -ls
> There is a screen on:
>         1072..rock      (Detached)
> 1 Socket in /tmp/screens/S-abb.
> 
> sh-3.2# screen -r
> ...

Alexandre, thanks for the report.  I've never tried to start screen in
detached mode before, so I never enountered this.  But I can confirm it
here.  For me the results are a little different-- the terminal doesn't
hang, but it stops echoing keyboard input and newlines.  I have to run
'reset' to get it working again.  And after that, screen -ls lists the
detached session as dead.

Clearly this is a bug in screen, and it seems to be specific to Cygwin.  I
can't reproduce it on my Ubuntu host.

Unfortunately, this is likely to be hard to solve.  I don't have the
knowledge or time to debug it myself.  You can report it to the
screen-users mailing list, but since it appears to be Cygwin-specific,
they're likely to send you back here.

Sorry.  There is something about the way screen uses sockets that doesn't
work completely right in Cygwin, and no one has ever figured out what it
is.  Mostly it does work right, and with the release of Cygwin 1.7 I'd
hoped we were done with it.

Andrew.


--
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

- Raw text -