Dear all,
Thank you very much for your help sofar.
The version I am using is 1.0.6, and as Milan pointed out, this version has
this behaviour.
Before doing anything else I will upgrade to see if this helps.
Ali
----- Original Message -----
From: "Milan Broz" <mbroz@xxxxxxxxxx>
To: "Thomas Bächler" <thomas@xxxxxxxxxxxxx>
Cc: <dm-crypt@xxxxxxxx>; "Ali Reza Sajedi" <arsajedi@xxxxxxxxxxxxx>
Sent: Thursday, March 25, 2010 6:28 PM
Subject: Re: Long Unlocking Time
On 03/25/2010 06:10 PM, Thomas Bächler wrote:
Am 25.03.2010 17:22, schrieb Milan Broz:
In my opinion, udev is the right place for such tasks, unless you want
to use or even write a daemon that listens for events using libudev -
which is overkill for such an easy task.
Udev rules should maintain /dev, not run time expensive operation which
will block all following events for the device.
Anyway, all I want to say is:
with cryptsetup 1.0.6 it will deadlocks because of internal "udevadm
settle",
and this is what you are probably seeing. You cat try update if you have
this version.
Milan
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
