[lkml]   [2009]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup)
On Fri, Jun 19, 2009 at 02:52, Robert Hancock<> wrote:
> On 06/17/2009 07:39 AM, Alexander Holler wrote:

>> The problem is that when I'm e.g. calling modprobe loop, loop might not
>> has finished it's initialization, when modprobe returns.
> It will have. Just that udev won't have received the events and created the
> device node yet. So the solution would likely be on the udev side..

The brutal method to do this is to call:
udevadm settle
after loading the module. It will block until all currently pending
events for udev are fully handled.

Recent udevadm versions also have a:
option, which will make "settle" stop waiting if a given file exists.


 \ /
  Last update: 2009-06-20 21:25    [W:0.073 / U:0.380 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site