Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53687 - [openssh] Please set 'KillMode=process' in sshd@.service
Attached to Project:
Arch Linux
Opened by Eric Wang (enihcam) - Sunday, 16 April 2017, 14:03 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 18 April 2017, 06:18 GMT
Opened by Eric Wang (enihcam) - Sunday, 16 April 2017, 14:03 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 18 April 2017, 06:18 GMT
|
DetailsDescription:
Processes get killed at the end of the session from socket activation. It gets killed by systemd when it notices that the SSH session process exited. The solution is to set KillMode=process in the Service section of ssh@.service. The KillMode=process setting already exist in the classic ssh.service, as it avoids killing the SSH session process or the screen or tmux processes when the server gets stopped or restarted. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: 1. systemctl enable sshd.socket 2. restart 3. screen and detach from a SSH session 4. exit 5. connect to the session again, and you see nothing is left. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Tuesday, 18 April 2017, 06:18 GMT
Reason for closing: Implemented
Additional comments about closing: in SVN
Tuesday, 18 April 2017, 06:18 GMT
Reason for closing: Implemented
Additional comments about closing: in SVN