On Tue, 07.10.14 14:14, Michal Sekletar (msekl...@redhat.com) wrote:
Hence, if a container manager mounts everything properly, then mount_setup()
should be a NOP anyway...
In theory yes, but in fact not having /run mounted as tmpfs is default in the
docker
container. I have no strong
On 10/08/2014 07:40 AM, Lennart Poettering wrote:
On Tue, 07.10.14 14:14, Michal Sekletar (msekl...@redhat.com) wrote:
Hence, if a container manager mounts everything properly, then mount_setup()
should be a NOP anyway...
In theory yes, but in fact not having /run mounted as tmpfs is
On Thu, Oct 02, 2014 at 11:43:22AM +0200, Lennart Poettering wrote:
On Thu, 02.10.14 09:57, Michal Sekletar (msekl...@redhat.com) wrote:
In cases when we are running as system manager, but we don't have the
capability to mount filesystems don't call mount_setup(). However we
assume that
In cases when we are running as system manager, but we don't have the
capability to mount filesystems don't call mount_setup(). However we
assume that some directories (e.g. /run/systemd) are always
around. Hence don't create those directories in mount_setup().
---
src/core/main.c| 7
On Thu, 02.10.14 09:57, Michal Sekletar (msekl...@redhat.com) wrote:
In cases when we are running as system manager, but we don't have the
capability to mount filesystems don't call mount_setup(). However we
assume that some directories (e.g. /run/systemd) are always
around. Hence don't
