Any ideas what this is?

[Steve Scrimpshire]

[omar@desktop omar]$ screen -r

There are several suitable screens on:

9607.pts-2.desktop (Dead ???)

file5Zve7r (Dead ???)

5833.pts-0.desktop (Detached)

5986.pts-0.desktop (Detached)

Remove dead screens with 'screen -wipe'.

Type "screen [-d] -r [pid.]tty.host" to resume one of them.

[omar@desktop omar]$ screen -wipe

There are screens on:

9607.pts-2.desktop (Removed)

file5Zve7r (Removed)

5833.pts-0.desktop (Detached)

5986.pts-0.desktop (Detached)

2 sockets wiped out.

2 Sockets in /home/omar/tmp.

 

I'm sure it's nothing, but it intrigues me.

FWIW, I ran chkrootkit and rkhunter and both found nothing.

[ramfree17]

those are screens that have been detached and whose programs running in them has terminated, or the screen itself has been terminated by a signal. i get them all the time when i was running jboss/weblogic inside of them to prevent being killed by the HUP signal.

 

what happens is that screen creates sockets in the temp directory (usually with the pid id of the screen plus some additional descriptors). if screen fails to do the clean-up (such as when not terminated normally) then the sockets will be left in place. the next time you issue a resume in screen, it will see these leftover sockets but could not communicate with the screen that was previously using them.

 

either wipe or rm will do the trick. i prefer wipe so that screen cleans-up after itself. :)

 

ciao!

 

[edit] nah, i took a second look and missed out the bold lines. that will be nothing if you specified a name for the screens when you created them. otherwise, its better if you head off to the screen user list. :(

 

ciao!

Edited February 9, 2005 by ramfree17