[prev] [thread] [next] [lurker] [Date index for 2007/01/14]
<30>yosefk@rostov:~> screen -d -r
There are screens on:
7614.pts-2.rostov (Dead ???)
12001.pts-4.tomsk (Dead ???)
11610.pts-12.naryanmar (Dead ???)
Remove dead screens with 'screen -wipe'.
There is no screen to be detached.
Nice. Someone killed my screen at rostov. And it says there's a dead one at
tomsk. Although I've just used one and it looked very lively. Well, what do you
know, maybe I had two screens there. I do have two running directories there.
OK, let's be friendly to the environment and follow screen's advice (I wonder
why it doesn't do it itself though):
<33>yosefk@rostov:~> screen -wipe
...
3 sockets wiped out.
OK.
<1214>yosefk@rostov:~> ssh tomsk
<34>yosefk@tomsk:~> screen -d -r
There is no screen to be detached.
<35>yosefk@tomsk:~> screen -r
There is no screen to be resumed.
How unpleasant. No more `screen -wipe`. /Now/ I am grateful that it doesn't bury
the alleged bodies itself. Well, at least the process I ran under screen is
still alive, which is still better than a bare ssh session...
Waitaminnit. What do you mean "the screen is dead and the process is alive"? The
process should have been kill by a broken pipe.
<54>yosefk@tomsk:~> ps -fade | grep SCREEN
yosefk 12001 1 0 Jan07 ? 00:00:15 SCREEN
Aha! So there's a screen all right. But the little screen doesn't notice the big
SCREEN. Why? RTFM:
<55>yosefk@tomsk:~> man screen
-d -r ...
-d -R ...
-d -RR ...
-D -r ...
-D -R ...
-D -RR ...
OK. I think I'll pass at the moment. I have scripts to check the status of that
process. So I don't lose /that/ much. I'd like to know WTF is going on though.
Generated at 13:01 on 17 Jan 2007 by mariachi 0.52