[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 to shared ?

Thanks for your help.

BR,

Hongzhi.Song

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Hints for upgrading systemd on a running system

2018-02-22 Thread Lennart Poettering
On Mi, 21.02.18 08:10, Paul Menzel (pmenzel+systemd-de...@molgen.mpg.de) wrote:

> > Note that PID 1 itself is probably pretty Ok with such a massive
> > update in one step, but the unit files have been rearranged quite a
> > bit since then. Downstream distributions generally expect you to
> > reboot even between single-step distro updates, but this becomes much
> > more of a necessity if you jump even further.
> 
> But if reboot wouldn’t be an option, is there a way to get rid of not-found
> services?

stop them.

How did you upgrade your kernel without rebooting?

Note that there's also stuff such as dbus-daemon which cannot be
updated without rebooting.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel