On 04/09/14 05:37, Russ Allbery wrote: > Ximin Luo <infinity0@pwned.gg> writes: > >> When switching to systemd, the directory /var/run/sshd is not >> automatically created, causing the resulting service to fail. > >> A workaround is to manually create the directory with the right >> ownership, but I have not verified if this persists across restarts. > >> Please automatically create the directory if it does not already exist. > > You're the second person who has reported this. The previous person found > that this was a side effect of having a configured mount in /etc/fstab > that was failing due to the directory not existing (or being a symlink; I > forget which it was). Could this also be the case for you? > /var/run is a link to /run but that is normal. My system mounts all work fine. I do have a bunch of /media/x/y/z mounts that fail, but that is not easily fixable apart from removing it, but I don't want to do that. Besides, sysv-init worked fine with that set up. If this is indeed the reason why it is failing, it is still a bug in systemd (or the systemd service definition for openssh) that should be fixed. There is nothing that says I must have all-valid mounts in /etc/fstab during boot, nor should there be - that would be ridiculous. I filed a similar bug for lighttpd too, but I guess less people are paying attention to that. So there is something wrong either with systemd, or any guidelines/examples that openssh/lighttpd used to write their systemd service definitions. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Attachment:
signature.asc
Description: OpenPGP digital signature