Hi Colin,
Apologies for hijacking this ticket with an unrelated problem. You're
quite correct in saying openssh-server package "does the right thing."
For the record, my problem was (or appears to have been) triggered by a
failure to mount an unrelated tmpfs file-system (/var/spool/cups/tmp)
earlier in the boot sequence. This failure was because /var/spool/cups
was a symlink pointing to another partition. If the other partition was
not mounted when attempting to mount /var/spool/cups/tmp, the mount
would fail.
Removing the /var/spool/cups/tmp tmpfs entry in fstab "fixed" the
problem: on boot, the /run/sshd directory is created and sshd starts up
successfully.
I'll open a fresh ticket to discuss this problem with systemd since
their handling of directories (and tmpfs in particular) seems problematic.
Cheers,
Paul.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
