Dne 25. 07. 19 v 20:49 Julian Andres Klode napsal(a):
systems might have systemd as their normal init systems, but
might not be using it in their initramfs; or like Debian, support
different init systems.
Detect whether we are running on systemd by checking for /run/systemd/system
and then change the behavior accordingly.
Wouldn't it be better to simply disable compiling/using lvmetad on such systems
?
HEAD of 2.03 already dropped lvmetad anyway.
Do you need any sort of autoactivation in ramdisk ?
There is probably higher complexity.
pvscan was not moved into systemd service just for fun - there have been at
least 2 major mandatory points why 'pvscan' with autoactivation MUST NOT be
executed from udev rule directly (udev timeout)
So the proposed patch must be NAC-ked as it is - as it probably causing way
more troubles then it solves.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
