On 21/11/2007 Dick Middleton wrote: >> Do you have any evidence? > > I looked at the source - udevsettle has a default timeout of 180s.
Ok, good to know. I just opened a bugreport against udev asking for documentation of this default in the manpage. > I checked that udevsettle as the only function in a run program causes the > deadlock hangup. > > Here's a suggested text for documentation somewhere: > > "If cryptsetup is to be included in a run program as part of a udev rule > then it should be detached so it runs asynchronously. cryptsetup may > otherwise hang waiting on udevsettle." > > I think that's the end of that. Thanks for all your help. great. I enhanced the documentation in README.Debian, but as i'm not a native english speaker, I hereby ask you to proofread the text ;-) Cryptsetup and udev ------------------- As a workaround for some yet-to-be-fixed race condition in kernel, device-mapper or udev, cryptsetup currently runs udevsettle. This leads to problems if you invoke cryptsetup as part of a udev role. udevsettle waits until queued kernel/udev events are processed and the 'run programs' have finished. Due to cryptsetup itself being a 'run programm' in this case, this ends in a deadlock. Therefore cryptsetup should be detached directly after invokation, so that it runs asynchronously. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
