From Mexico.purplecow.org
(Difference between revisions)
(create) |
Current revision (14:53, 15 September 2010) (view source) |
||
Line 3: | Line 3: | ||
== Symptoms == | == Symptoms == | ||
- | You lost a session, probably when your laptop went to sleep or something. You try to <pre>screen -d -r</pre> from a new session and screen hangs. A truss shows that reattach process doing nothing but maybe <pre>pause</pre>. Ugly, huh? | + | You lost a session, probably when your laptop went to sleep or something. You try to <pre>screen -d -r</pre> from a new session and screen hangs. A truss shows that reattach process doing nothing but maybe <pre>pause</pre> with a few alarm signals. Ugly, huh? |
== Diagnosis == | == Diagnosis == |
Current revision
Hung GNU screen
Symptoms
You lost a session, probably when your laptop went to sleep or something. You try toscreen -d -rfrom a new session and screen hangs. A truss shows that reattach process doing nothing but maybe
pausewith a few alarm signals. Ugly, huh?
Diagnosis
Either the old attached process is still hanging around (check for the dead session by the old tty name) or another bastard has gone sour ...
utmp_update
This can hang and cause screen to wait forever. Killing it fixes it.
Prescription
fuser /tmp/screens/S-username/blah
Kill the unwanted process and you should be good to go.