Wouldn't a relative simple change to fix this would be explicit TriggerLimitBurst=0 until some form of timed reactivation is implemented? Especially for sshd.socket that change would seem safer. It is not a big deal for sshd, it seems to be quite small anyway.
Could simple
[Unit] Restart=on-failure
solve this issue instead? If it fails, this should be able to keep it up. Does it manifest itself a different way?
On 03. 08. 23 11:29, Dmitry Belyavskiy wrote:
Dear colleagues,
I've pushed a fresh build of OpenSSH to rawhide. We decided to drop the sshd.socket unit from rawhide. We don't think it's worth going through the changes process, but would like to provide a heads-up.
See the details in https://bugzilla.redhat.com/show_bug.cgi?id=2025716.