3 ms·

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

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.

jon-wood 1y ago
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.
jeroenhd 1y ago
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?
- blueflow 1y ago
  Unwarranted suspends by logind have always been a menace, i have been fighting them for a decade. > 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? sshd already links against systemd (by distro patches, not per upstream) but since SSH is a "legacy protocol" and its users are "uneducated troglodytes", this is not going to happen. I think this is because OpenSSH is an OpenBSD project, and both systemd and OpenBSD refuse to support each other.
  - wmanley 1y ago
    > SSH is a "legacy protocol" and its users are "uneducated troglodytes", Who are you quoting here?
    - bheadmaster 1y ago
      I assume that's a parody on systemd developers' attitude towards The Unix Way (TM). This github issue comes to mind: https://github.com/tmux/tmux/issues/428 https://github.com/tmux/tmux/issues/428

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.

jon-wood 1y ago

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.

jeroenhd 1y ago

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?

blueflow 1y ago
Unwarranted suspends by logind have always been a menace, i have been fighting them for a decade. > 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? sshd already links against systemd (by distro patches, not per upstream) but since SSH is a "legacy protocol" and its users are "uneducated troglodytes", this is not going to happen. I think this is because OpenSSH is an OpenBSD project, and both systemd and OpenBSD refuse to support each other.
- wmanley 1y ago
  > SSH is a "legacy protocol" and its users are "uneducated troglodytes", Who are you quoting here?
  - bheadmaster 1y ago
    I assume that's a parody on systemd developers' attitude towards The Unix Way (TM). This github issue comes to mind: https://github.com/tmux/tmux/issues/428 https://github.com/tmux/tmux/issues/428