My understanding (not having looked at the code - someone correct me if I'm wrong) is that it's split into two processes, effectively a client and server. When you start a new screen session, it spins up both, but only the client is associated with the terminal. So closing the terminal kills the client (as it should); the server lives on because it never got the HUP. When you attach a screen, it connects to a running server.
On Fri, Feb 21, 2014 at 11:17 AM, Michael Clark <mjclark...@gmail.com>wrote: > I'm fairly new to linux and I am just curious as to how screen manages to > survive the logout process. I don't know the logout process really works > either but I assume that screen manages to ignore the signal sent to all > the process I own when I logout. I thought that was SIGHUP but when I do > kill -HUP <screen pid> it kills the session. Can someone explain how this > works? > > _______________________________________________ > screen-users mailing list > screen-users@gnu.org > https://lists.gnu.org/mailman/listinfo/screen-users > >
_______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
