Michael, thanks for working on this and reporting to upstream.
Meanwhile I've mounted the mount points over tty1 and they are indeed
propagated to all services. But I think you already figured it out as
you tried to reproduce the bug.
For someone who doesn't have access to tty, the nsenter command can also
provide a workaround to provide mount points to specific services:
$ nsenter --mount --target <service-pid>
$ mount --make-shared /dev/mapper/<mount> /mnt/<mount point>
$ exit
On 2017-12-29 23:22, Michael Biebl wrote:
Am 29.12.2017 um 13:03 schrieb Sumit Madan:
I'll try that tomorrow evening and inform you; I'm not at home
currently. But what I can tell is that the behavior over SSH has been
changed. In the past I often created mounts over SSH.
My guess is that this is related to this upstream change
https://github.com/systemd/systemd/commit/652bb2637aee54e3503a22d2928a929ecd7a84b3
and ssh.service using
RuntimeDirectory=sshd
RuntimeDirectoryMode=0755
See https://github.com/systemd/systemd/issues/7761#issuecomment-354507016
--
Mit freundlichem Gruß,
Sumit Madan
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
