On 5/12/2016 7:24 AM, Pann Tolk wrote:
I believe I have found the cause of the problem posted earlier.
Apparently, systemd isolates processes launched by udev by putting
them into a different mount namespace, which prevents new mounts from
propagating back to the main namespace. So, by default mounts done
within udev .rules do not propagate back to the host.
To fix this problem, I need to edit the "MountFlags=" in
"/usr/lib/systemd/system/systemd-udevd.service". Changing it from
"MountFlags=slave" to "MountFlags=shared" solved the problem.
However, I'm not sure if this permanently fixes the problem...ie not
sure if the next update will cause the change to revert back to
original setting.
Nice work finding that! I never expected that systemd would get so
involved with the OS. The more I deal with systemd, the less I like it
and the more it reminds me of Windows WININIT.
This almost certainly has to do with docker, which perhaps needs slave
mode to prevent an unexpected umount. But why can't this setting be in
/etc/systemd/system.conf? My bet is that everything in /usr/lib/systemd
can and will be overwritten by an update.
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
