[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: screen refusing to reattach

From: Buddy Burden
Subject: Re: screen refusing to reattach
Date: Sat, 02 Apr 2005 15:06:54 -0500
User-agent: Mozilla Thunderbird 0.8 (Windows/20040913)


Yes, kill off the shell associated with the pty/tty running "screen".  I
found that killing off screen by itself doesn't cut it...

Okay, this just happened to me again, and Jeremy's suggestion didn't do the trick. I thought I'd take a moment while this was fresh in my mind to describe ANAICT the exact sequence of events.

1) The window I'm currently working in locks up. On this particular occasion I had been away from the term, but only for a minute or so.

2) I can switch to other windows and they appear to be responding correctly.

3) I return to the locked up window and kill it. I get the "do you really want to kill this window prompt". I hit 'y'. The window disappears, but then screen is locked (with the "do you really" prompt still there). "Locked" in this case means no key appears to do anything.

4) I kill the term.

5) In a new term, I check the processes. I have one screen -s running in an Eterm (that's on the base machine), two screen -x's running in -tcsh's (from who knows where), and one orphaned screen -x (presumably the one I was just running here on my off-site machine). (That's not including the screen processes related to my completely separate screen session, which is never impacted by the first session crashing horribly.) Oh, and also of course one SCREEN.

6) I kill the orphan screen -x first, then kill the -tcsh's that are parenting the other screen -x's, then kill the freshly orphaned screen -x's. The -tcsh's require kill -9's (typical for a login shell IME), but the screen processes go nicely.

7) Try to reconnect with screen -x, no go. Now kill the Eterm and the screen -s as well. Try screen -x, screen -d, screen -D, and screen -DD; all just hang (but respond to Ctrl-C). A screen -ls shows the session is "attached".

8) Sighly dramatically, kill -9 the SCREEN. This removes the session from screen -ls and I can start fresh with a new screen -s.

So does anyone have any thoughts on why this occurs and how to stop it?

                -- Buddy

reply via email to

[Prev in Thread] Current Thread [Next in Thread]