Skip to content
Advertisement

Killing a screen without a specific session #

To create a screen, I am currently doing:

JavaScript

That works perfectly, however killing it remotely with:

JavaScript

Will reply with:

JavaScript

This is due to the screen having {session#}.{screenname}

It will work if done as:

JavaScript

What solutions are possible? I’m not entirely sure that you can get the session# when you start the screen. This is all done remotely too.

Advertisement

Answer

I also start screens with the -dmS option, and I send commands to the screen using the stuff command:

JavaScript

more details on “stuff” are in the screen man page, search for ‘stuff string’

User contributions licensed under: CC BY-SA
2 People found this is helpful
Advertisement