Bug#728486: Current patch for resolving lvm/systemd compatibility
On Sat, Jan 18, 2014 at 11:33:32PM +0100, Michael Biebl wrote:
> On Sat, Jan 18, 2014 at 01:20:41PM +0100, Bastian Blank wrote:
> > - lvm2.service is statically hooked to local-fs.target, as all local
> > mounts.
> lvm2.service is not a local mount, so that is not really a justification for
> enabling the service statically.
Please show me a better target. This is what the generator does, so I
assume there exists none.
> > +ExecStartPre=/bin/udevadm settle
> Please don't run udevadm directly. This is a udev command.
Can you please describe what will be broken by this?
> Wants=systemd-udev-settle.service
> After=systemd-udev-settle.service ...
> (as the original .service file does).
The generated service files uses both variants:
- The pre-cryptsetup and pre-local-fs services uses
systemd-udev-settle.service.
- The pre-remote-fs service, which is not included here currently, uses
ExecStartPre.
> Wants= will make sure the systemd-udev-settle.service is started
> dynamically and After= ensures the correct ordering.
It only makes sure that systemd-udev-settle.service was started
somewhere _before_. It does however not make sure it is called again
for the second round or third round.
Bastian
--
You! What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0
Reply to: