3 ms·
This is a good feature, and a good default. Processes in the session-xx.scope should be stopped when the session ends. there's an easy sollution for processes
by gdamjan1 10y ago
This is a good feature, and a good default.
Processes in the session-xx.scope should be stopped when the session ends.
there's an easy sollution for processes that don't need to be stopped too.
- caf 10y agoNo, there was already a mechanism in place to end processes when you log out - when the controlling tty disappears, every process in the session is sent a SIGHUP and SIGCONT signal. The processes started under screen(1) are deliberately created with a new pty as controlling tty and in a new session, because they are intended to survive the ending of the original session where screen was started.
- gdamjan1 10y agonot for processes that don't have a controlling tty. processes deliberatelly started with screen can be started with systemd-run screen.