X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,TW_SR X-Spam-Check-By: sourceware.org Date: Sun, 8 May 2011 14:40:37 -0500 From: Doug Morse To: cygwin AT cygwin DOT com Subject: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try Message-ID: <20110508194037.GA15550@ikrg.com> Reply-To: Doug Morse Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, Any assistance most appreciated (see below)! Thanks, Doug ----- Forwarded message from Doug Morse ----- Date: Sat, 07 May 2011 16:06:48 -0500 From: Doug Morse To: Andrew Schulman Subject: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try Hi Andrew, Thanks so much for your efforts to port and maintain the GNU screen program to Cygwin! I used to use screen all the in the pre-GUI days, and now I use ssh regularly for the occasions I need to run something on a real win32 or win64 platform. Being able to use screen again would be great, especially because I routinely get disconnected from one machine in particular due to a lousy DSL line. At any rate, although I can run screen just fine, I cannot reattach, no matter what I do, even when there's been no disconnect and I've simply manually detached (i.e., Ctrl-A d). The session log below pretty much says it all. Note that I move my .screenrc file out of the way to ensure I'm running with nothing but default settings. Also, you'll notice in the output from "ps aux" that the "screen" process, once detached, has a tty value of "?", whereas all the others have a tty number. Other than this, though, everything works just as one would expect. Processes continue to run fine under screen even when detached: I simply just cannot reattach. As you can also see below, doing a "kill -15" on screen causes it do a proper shutdown and remove the socket file. Odd, very odd. Any thoughts? Finally, please pardon me in advanced if I should have posted this somewhere instead of emailing you directly. I could not find a forum or irc or website indicating where to report this / ask for help. Happy Weekend! Thanks, Doug ----- begin session log ----- morse AT dougsdell ~> screen --version Screen version 4.00.03 (FAU) 23-Oct-06 morse AT dougsdell ~> uname -a CYGWIN_NT-5.1 dougsdell 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin morse AT dougsdell ~> mv .screenrc screenrc morse AT dougsdell ~> screen [ <--- I press Ctrl-A d here ] [detached] morse AT dougsdell ~> screen -r There is a screen on: There is no screen to be resumed. morse AT dougsdell ~> screen -ls There is a screen on: 1 Socket in /tmp/uscreens/S-morse. morse AT dougsdell ~> l /tmp/uscreens/S-morse/ total 16 srw-r--r-- 1 morse None 0 May 7 15:45 3932.tty1.dougsdell morse AT dougsdell ~> screen -r 3932.tty1.dougsdell There is a screen on: There is no screen to be resumed matching 3932.tty1.dougsdell. morse AT dougsdell ~> ps aux PID PPID PGID WINPID TTY UID STIME COMMAND 2396 1 2396 2396 con 1005 22:59:53 /usr/bin/rxvt I 2412 2396 2412 2428 0 1005 22:59:53 /usr/bin/bash 2080 3408 2080 1780 1 1005 15:41:47 /usr/bin/bash 3932 1 3932 3932 ? 1005 15:45:49 /usr/bin/screen I 3376 3932 3376 3460 2 1005 15:45:49 /usr/bin/bash 2168 2080 2168 2212 1 1005 15:46:32 /usr/bin/ps morse AT dougsdell ~> kill -15 3932 morse AT dougsdell ~> ps aux PID PPID PGID WINPID TTY UID STIME COMMAND 2396 1 2396 2396 con 1005 22:59:53 /usr/bin/rxvt I 2412 2396 2412 2428 0 1005 22:59:53 /usr/bin/bash 2080 3408 2080 1780 1 1005 15:41:47 /usr/bin/bash 2228 2080 2228 2076 1 1005 15:46:45 /usr/bin/ps morse AT dougsdell ~> screen -ls No Sockets found in /tmp/uscreens/S-morse. morse AT dougsdell ~> l /tmp/uscreens/S-morse/ total 0 morse AT dougsdell ~> echo "help! :)" help! :) ----- end session log ----- ----- End forwarded message ----- -- 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