Comment 10 for bug 1814124

Revision history for this message
Robie Basak (racb) wrote : Re: sshd does not start after update

> The entry in /usr/lib/tmpfiles.d/sshd.conf SHOULD be...

I don't agree, even if this happens to work for you. It's valid for it to be /var/run/sshd provided that your system is properly up-to-date (see related bug 1804847). If you're using some environment that is broken, please ask the people who develop that environment to fix the problem.

I'm reluctant to "just" proposed to change it the other way in a stable release, because other users may be regressed in other ways by that change. If your system is broken in this behaviour, it may be broken in other ways too that will manifest later.

Since there's no action planned to be taken in Ubuntu for this behaviour, I'm marking the bug status Invalid to make this clear to users.

For users with broken systems, the workaround for this specific symptom (rather than the general problem) is to override your tmpfiles.d entry in /etc/tmpfiles.d. DO NOT EDIT /usr/lib/tmpfiles.d/sshd.conf since this will be overwritten in a future package update. The right way to make local configuration changes is in /etc/tmpfiles.d/. See tmpfiles.d(5) for details. I'd appreciate if somebody could test and provide step-by-step instructions to help other users.