Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-03-02 Thread Lennart Poettering
On Fr, 02.03.18 10:22, Hongzhi, Song (hongzhi.s...@windriver.com) wrote: > On 2018年03月01日 17:50, Lennart Poettering wrote: > > On Do, 01.03.18 14:44, Hongzhi, Song (hongzhi.s...@windriver.com) wrote: > > > > > Thank you very much. It dose work. > > > > > > Would you tell me that how the

Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-03-01 Thread Hongzhi, Song
On 2018年03月01日 17:50, Lennart Poettering wrote: On Do, 01.03.18 14:44, Hongzhi, Song (hongzhi.s...@windriver.com) wrote: Thank you very much. It dose work. Would you tell me that how the '--no-block' works, "systemd-mount" talks to systemd (i.e. PID 1) to issue mount/automount operations. By

Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-03-01 Thread Lennart Poettering
On Do, 01.03.18 14:44, Hongzhi, Song (hongzhi.s...@windriver.com) wrote: > Thank you very much. It dose work. > > Would you tell me that how the '--no-block' works, "systemd-mount" talks to systemd (i.e. PID 1) to issue mount/automount operations. By default it will do so synchronously, thus

Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-02-28 Thread Hongzhi, Song
Thank you very much. It dose work. Would you tell me that how the '--no-block' works, I doesn't deeply understand the interpretation in https://www.freedesktop.org/software/systemd/man/systemd-mount.html#SYSTEMD_MOUNT_OPTIONS= And why systemd-mount can solve the problem brought by

Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-02-27 Thread Andrei Borzenkov
27.02.2018 17:20, Hongzhi, Song пишет: > Hi, > > thank for your help, but I still have some question. > > > My current linux system init uses systemd and udev, with > 'automount.rules' and 'mount.sh' in /etc/udev/, > > to manage device. But owning to MountFlags=slave, hotpluggable media >

Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-02-27 Thread Hongzhi, Song
Hi, thank for your help, but I still have some question. My current linux system init uses systemd and udev, with 'automount.rules' and 'mount.sh' in /etc/udev/, to manage device. But owning to MountFlags=slave, hotpluggable media (e.g., /dev/sda1 ) can be mounted again in host, whereas

Re: [systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-02-23 Thread Lennart Poettering
On Do, 22.02.18 20:52, Hongzhi, Song (hongzhi.s...@windriver.com) wrote: > Hi, > > systemd, upstream commit id c2c13f2df42e0691aecabe3979ea81cd7faa35c7 > > You set MountFlags=slave just for keeping mounts done by udev rules private > to udevd. > > So all block device mounted by systemd-udevd

[systemd-devel] Why did you set MountFlags=slave in systemd-udevd.service.in

2018-02-22 Thread Hongzhi, Song
Hi, systemd, upstream commit id c2c13f2df42e0691aecabe3979ea81cd7faa35c7 You set MountFlags=slave just for keeping mounts done by udev rules private to udevd. So all block device mounted by systemd-udevd is unvisible for host. I don't know why. And is there any bad effect, if I change slave