cryptmount

Thanks for the suggestion.

I have already considered using "udevadm settle", but this command is not
available on all the flavours of Linux I have used for testing cryptmount,
and may not be available in older versions of the udev package. For this
reason, the cryptmount executable uses a simple test on /dev/.udev/queue,
while the startup scripts try "udevadm settle" before trying "udevsettle",
or falling back on "sleep 5".

I am not clear from your message whether the search for "udevsettle" is
actually preventing cryptmount from working sensibly. Perhaps you could
supply more details about what's actually happening, with which particular
version of cryptmount, and under what circumstances?

Thanks.