On 19/11/2007 Dick Middleton wrote: >>> I suspect that udevsettle is the one you added to cryptsetup. Maybe a >>> timeout would fix this? >> >> udevsettle indeed supports a --timeout= option, and this would >> workaround your delay. > >> maybe the reason for your 3 minutes delay is that udevsettle has a builtin >> timeout of 3 minutes. > > That was my assumption.
Do you have any evidence? if so, i will happily add a timeout to the udevsettle invokation in cryptsetup. >> in that case i have no problems with lowering the timeout of 30 seconds or >> something like that. > > I was thinking something more like 5 or even just 1. However as I think > the udevsettle is waiting for itself to complete I've tried spawning the > cryptsetup in my script in a separate shell so it runs asynchronously > allowing the run rule script to complete. > > It seems to work - I'm not sure what problems might appear! > > So that's my particular problem solved but obviously running udevsettle > from within a program is problematic. can you elaborate on this? in my eyes the reason to invoke udevsettle is to go sure that relevant udev events have finished. we need to know how long these events delay in really bad situations to figure out a sane timout value for udevsettle. if some situations cause the events to hang for i.e. 3 secs, a timeout of 1 second would be to short. so as long as we don't know more about that, i would really like to check first if udevsettle has a builtin timeout at all. maybe the 3 minutes delay is a problem on your side, and the udev events really take the full 3 minutes to process? if on the other side the 3 minutes are due to a builtin timeout in udevsettle, lowering this timeout to a safe value like 20 or 30 secs should be no problem. greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
