Op 16-09-2022 om 09:17 schreef Michael:
with ssh@.service it is completely different. for each connection there is a dedicated sshd process being started, and each one of them has the same /run/sshd directory assigned. and that's the problem if you have more than one connection to a given host. as soon as the first connection is terminated, the /run/sshd directory disappears, and the other sshd's might run into problems.
Apparently this has already been 'fixed' for bookworm. That is, the service section of the ssh@.service file currently includes RuntimeDirectoryPreserve=yes. Maybe file a bug report to have this added for bullseye? Regards, Frank