Jonas Meurer wrote:
I prepared cryptsetup packages with the proposed patch applied. could
you give them a try?
I just submitted this as a bug to udev (451702) completely forgetting
the workaround recently made to cryptsetup. So FYI:
--
I have a run rule script which checks a block device for being luks
and if so runs cryptsetup to create a dm-crypto map. This has worked
fine for ages but now I find it hangs for exactly 3 minutes. The
following processes exist for this period:
30447 ? S< 0:00 udevd --daemon
30457 ? S< 0:00 /bin/bash /etc/udev/scripts/usbluks.rr OPTIONS=
30462 ? S<L 0:00 /sbin/cryptsetup -d /etc/keys/akasa2 luksOpen
/dev/usb/akasa2 akasa2
30465 ? S< 0:00 /sbin/udevsettle
What seems to be happening is that cryptsetup is creating a new
device. As a result udev runs udevsettle but that doesn't exit until
timeout. Once udevsettle completes the run rule completes.
--
I suspect that udevsettle is the one you added to cryptsetup. Maybe a
timeout would fix this?
Dick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
