206

I'm trying to kill a screen session. I noticed a lot of other related questions, but none of those answers are working for me. I am trying to kill the following session:

screen -ls
There is a screen on:
    23520.pts-6.porkypig    (09/30/2013 02:49:47 PM)    (Detached)
1 Socket in /var/run/screen/S-root.

screen -r 23520.pts-6.porkypig

Now I am in the session. According to the documentation:

http://www.gnu.org/software/screen/manual/screen.html#Quit

I am supposed to press "control a" and then "control \". I do that and nothing happens.

Another solution said to press Ctrl+a and type :quit. However, again it doesn't do anything. In fact, pressing control+a, absolutely nothing happens afterwards except a message "No Other Window"

slava
  • 3,887
JohnMerlino
  • 7,309

13 Answers13

250
  1. Identify the name of the session:
 $ screen -ls
  1. Close a session:
$ screen -XS <session-id> quit
  • Rationale: -X = Execute command, -S session PID to execute on
  • Example: screen -XS 20411 quit
  • Source: innaM's Answer
shgnInc
  • 4,003
223

first you need to re attach to the screen session
screen -r 23520 as you have done. Then press ctrl + a and then a k and press y when it asks if you really want to kill the session

Source

Ben
  • 998
17

This command will kill all screen sessions, if that is desired:

So with all those official suggestions, I have one here that i feel is easier, and just as effective, and kind of more straight forward:

pkill screen

Who wants to go into an unknown and un-needed screen just to press in a couple commands that most might barely remember? This avoids going into it at all, and kills it straight off.

Plus, if you have more than one, this will take them all in one fell swoop.

  • 7
    Note that this will kill all running screens, which may or may not be what you want. – Mikkel Sep 26 '16 at 14:57
  • 2
    Not a good choice. I've been doing it for some time. Sometimes it causes bad behaviors (e.g. logging out from your user account immediately). Also, as @Mikkel mentioned, it could cause to close all your screens, which would not be what you want. Sometimes you need to keep running some (e.g. some are running by system) and stop some other screens. – MAChitgarha Sep 04 '18 at 05:14
12

Like you, I wanted to kill my screen session and found the documentation unhelpful. Convinced that there must be a keyboard shortcut, I found that
ctrl + a then \
works

I then get the prompt: "Really quit and kill all your windows [y\n]"

I am not sure why the documentation says ctrl + a then ctrl + \. That doesn't do anything for me.

lizp
  • 121
10

This will kill all the detached screens:

screen -ls | grep detached | cut -d. -f1 | awk '{print $1}' | xargs kill

This will kill all screens, attached or detached

screen -ls | grep pts | cut -d. -f1 | awk '{print $1}' | xargs kill
Adaephon
  • 4,891
  • Is the awk step really necessary? – Martin J.H. Jul 27 '22 at 08:05
  • I am an grep/awk/xargs noob and always will be. But based on your answer I built my own shell alias. Just in case this may be useful for someone: alias killscreen='screen -ls | grep -i attached | awk '\''{print $1}'\'' | xargs -L1 bash -c '\''screen -XS $0 quit'\''' (kills all attached sessions) – Matthias W. Dec 25 '23 at 12:23
5

You can use this to kill a session

screen -X -S <name> kill
4

we can also use the exit command to terminating screen

  • Easiest and most straightforward approach! You will, of course, first need to reattach to the screen session. – gillesC Jul 16 '21 at 08:36
3

You can find the process id of the attached running screen. I found it same as the session id which you can get by command:
screen -ls
And you can use following command to kill that process:
kill [sessionId] or
sudo kill [sessionId]
You can kill the screen even if it is attached on some other terminal window.

3

I encountered this problem when updating screen. The screen command would hang when attempting to reattach the session, regardless of how many -D or -R I added to the command. However, screen -ls conveniently provides the pid of the session, allowing you to intervene using the following:

10:42 user ~ $ screen -ls
There is a screen on:
        5730.my_screen     (Detached)
1 Socket in /tmp/screens/S-user.

10:42 user ~ $ sudo kill 5730

10:43 user ~ $ screen -ls
No Sockets found in /tmp/screens/S-user.

(This is similar to Brian Thomas's answer, but his will kill all running screen sessions, which may not be what you want if you have multiple screens open but only one misbehaving.)

Mikkel
  • 343
  • After 6 hours breaking my head all over internet... yours was the only answer that worked. Thanks mate! – kRazzy R Sep 30 '17 at 06:43
0

Press ctrl+d to kill screen window. Repeat this until you kill all screen windows. Once you ran out all windows screen will kill the session and terminating. Shortest solution if you not having many windows

0

You can just simply type exit while in a recording mode, I found out it to be most convenient as it directly exits the running screen.

0

Simply, use the exit command inside a screen window and if you have a running process press control + z before that.

  • This doesn't answer the question (how to kill a screen session, as opposed how to exit normally) and it doesn't expand on the other answers. A good answer might cover the normal exiting procedure and then document a few ways you can kill screen if that doesn't work. – Coljac Mar 02 '22 at 22:38
0

I believe what is being asked is how to 'quit' a screen session from within screen itself. This would kill all open terminals in the session and leave the user at the prompt for the parent terminal. The session can be suspended from within using CTRL-A, CTRL-Z. But this creates a a problem I'm trying to avoid which is leaving a bunch of opened screen sessions over time and then not knowing which ones are truly active and which ones I should have closed.

After lots of looking, I believe there is no way to do this. Killing them using the PID method is ok, but if there are many sessions open, some of which I might be using, I don't always know which ones to kill.

So what I do when I'm truly done with a screen session is to repeatedly hit CTRL-d to close each terminal individuly until the session completely exits.

This is the best solution I've found.