▲ | blueflow 4 days ago | |||||||||||||||||||||||||
Of course systemd killing your SSH session is a intentional feature, not a bug. Consider disabling suspend from the logind.conf and suspend, if at all, only at explicit user request. | ||||||||||||||||||||||||||
▲ | jeroenhd 4 days ago | parent | next [-] | |||||||||||||||||||||||||
systemd doesn't kill your SSH session (if you'd WoL your PC there's a good chance you can continue typing unless your local terminal detects that the other end goes down). It's more that when you configure systemd to suspend your computer when there is no physical activity, it will suspend your computer when there is no physical activity. The author wants their computer to suspend automatically. I think modifying your system configuration to never suspend is a much worse solution than using the tool designed to prevent suspending the computer while a specific program is running to prevent suspending the computer while that specific program is running. It'd be easier if `sshd` would permit you to wrap the incoming command line/shells so `sshd` would spawn your session with systemd-inhibit, but I don't think that's possible? | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | jon-wood 4 days ago | parent | prev [-] | |||||||||||||||||||||||||
I think the author’s point was that this is usually desired behaviour because it’s a desktop and only occasionally do they want to stop that. |