And if you name the session it is easy to do withoutknowing the pid which
varies each time it is started.
On Mon, 26 Sep 2016, Jim Mahood wrote:
If you know the pid, simply killing it with whatever signal you want would
be most efficient.
On Sep 26, 2016 6:08 PM, "Jostein Berntsen" <jber...@broadpark.no> wrote:
On 26.09.16,19:11, Jostein Berntsen wrote:
On 26.09.16,14:17, Colin Richardson wrote:
I am attempting to break a nodejs application that is running in a
detached
screen. (From another screen nodejs application).
But I am falling over at the first hurdle in just trying to send a break
command in the first place.
I am doing ` screen -S ser02 -X "^C" `
But when I do ` screen -r ser02 ` node is still running.
I tried a few other things such as ` ^A b ` thinking it would be using
the
internal screen commands.
Can you check if this works?
screen -S ser02 -X 'stuff " "'
Or will this be the most efficient way?
screen -S ser02 -X quit
Jostein
_______________________________________________
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users
[ Part 2: "Attached Text" ]
_______________________________________________
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users
XB
_______________________________________________
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users
