Bug#885325: Similar issue: Mount points not found by apache2 and another services

2017-12-31 Thread Sumit Madan
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

Bug#885325: Similar issue: Mount points not found by apache2 and another services

2017-12-29 Thread Michael Biebl
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

Bug#885325: Similar issue: Mount points not found by apache2 and another services

2017-12-29 Thread 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. On December 29, 2017 10:32:06 AM GMT+01:00, Michael Biebl wrote: >Am 29.12.2017 um 01:28

Bug#885325: Similar issue: Mount points not found by apache2 and another services

2017-12-29 Thread Michael Biebl
Am 29.12.2017 um 01:28 schrieb Sumit Madan: > Do you have an idea how to propagate the mount points created in an ssh > session to other namespaces? Just to clarify: This issue only happens if you login via SSH? If you login locally, e.g. on tty1, the manually mounted mount points are visible

Bug#885325: Similar issue: Mount points not found by apache2 and another services

2017-12-28 Thread Sumit Madan
Dear Maintainer, I've got a similar issue with mount points that are mounted manually after the boot process is completed. As John reports these mount points are not reachable anymore from other services. In his case smbd and in my case apache2 is affected. I think the issue here is with