[libvirt] [PATCH 2/2]: Call udevsettle in the appropriate places

Alan Pevec apevec at gmail.com
Fri Nov 28 13:15:57 UTC 2008

On Thu, Nov 27, 2008 at 8:53 AM, Chris Lalancette <clalance at redhat.com>wrote:

> Right, both points make sense.  I think the following patch should address
> it; I
> only conditionally set the UDEVADM variable if I find it.  So, for machines
> without it, the meat of virStorageBackendWaitForDevices is compiled out.
>  In
> places where I've found it on the build machine, I then do "access" for
> executable at runtime, and only if that succeeds do I run it.  Does that
> seem
> correct?  In addition, based on the comment from Guido, I changed it over
> to use
> "udevadm settle" instead of "udevsettle".

Please make it try both: RHEL5 has an ancient udev095 and doesn't have
udevadm but it does have udevsettle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20081128/11e6fbe1/attachment-0001.htm>

More information about the libvir-list mailing list