Bug#760422: openssh-server: systemd service does not automatically create /var/run/sshd
tags #760422
> As a workaround, I believe adding the "nofail" option to mounts that may
> or may not succeed will make the problem go away.
Unfortunately, this only makes a different problem surface.
With "nofail", systemd will initiate the mount, sent it to the
background and immediately continue booting. This will cause the
local-fs.target to be "reached" while there is still a mount in
progress in the background, which might take a few seconds, for
example if a journal needs to be replayed. This will also apply to a
separate /var.
This will, in turn, cause other units such as
systemd-tempfiles-setup.service to be started with /var not yet
present, which will in turn cause /var/run/sshd to be created on the
root fs instead of the mounted fs, which is then prompty overlaid by
the "real" /var file system, which has a symlink from /var/run to
/run, but /run/sshd is not yet there, resulting in a non-operational
sshd.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Reply to: