I typically log into my Linux box from my Windows laptop using PuTTY and run screen there. When my corporate overlords decided to update my laptop to Windows 7 my PuTTY sessions have been freezing. I typically kill the PuTTY session and then either reattach the screen session (if it detached) or issue a "-d -r" if the screen session didn't detach when my PuTTY session froze up.
My problem is that I have a screen session that, at first, refused to detach. I'd use:
screen -d -r 6313.sessionName
but the command would just hang there.
I found that in the /var/run/screen// directory were "files" corresponding to each of my screen sessions. I noticed that the stubborn one had 700 permissions on it while the others (which were detached) had 600 permissions.
So I changed the permissions on that file to 600. Screen now lists it as "detached". However when I try to reattach to it the command, once again, just hangs there.
Using
ps aux | grep 6313
shows the process state as "Ss", which means it's in an interruptable sleep state. This is no different than any of the other detached screen sessions which show the same process status.
I'm at a loss as to how to recover this session. Any suggestions?
screen -S <name>
so that every session has a name I know. That way, when I want to disconnect and reconnect, I can use that name instead of a PID, such asscreen -r <name>
orscreen -dr <name>
mysession
instead ofpid.mysession
.-S
flag, you should be able to reference just themysession
with no need for the pid prefix.