[systemd-devel] [ANNOUNCE] systemd 219
Lennart Poettering
lennart at poettering.net
Tue Feb 17 02:08:57 PST 2015
On Tue, 17.02.15 06:53, Andrei Borzenkov (arvidjaar at gmail.com) wrote:
> В Mon, 16 Feb 2015 23:59:56 +0100
> Lennart Poettering <lennart at poettering.net> пишет:
>
> >
> > * When a .mount unit refers to a mount point on which multiple
> > mounts are stacked, and the .mount unit is stopped all of
> > the stacked mount points will now be unmounted until no
> > mount point remains.
> >
>
> Does it mean that in either of below case
>
> mount something-else /foo
> systemctl start foo.mount
In this case the second line is a NOP, since the first line already
mounted something on /foo, and thus made foo.mount active.
(Also, small hint, you can just write "systemctl start /foo", it will
be implicitly converted to "systemctl start foo.mount".)
>
> and
>
> systemctl start foo.mount
> mount something-else /foo
This one will result in too mounts one on top of the other.
> systemctl stop foo.mount will also unmount something-else?
Correct. In the first case a single mount is removed, in the second
case two mounts will actually be removed.
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list