From: Farkas Levente <lfarkas@lfarkas.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problem with udevsettle
Date: Thu, 03 Jul 2008 20:54:31 +0000 [thread overview]
Message-ID: <486D3C87.4040207@lfarkas.org> (raw)
In-Reply-To: <486CD00A.3040800@lfarkas.org>
Bryan Kadzban wrote:
> You shouldn't call cryptsetup from the udev RUN key. From the udev(7)
> manpage:
>
>> RUN
>> <...> This can only be used for very short running tasks. Running an
>> event process for a long period of time may block all further events
>> for this or a dependent device. Long running tasks need to be
>> immediately detached from the event process itself.
>
> When your RUN rule is executed, udev is in the middle of processing the
> uevent for the USB storage device. So while your script is running,
> udev has not settled (the test that udevsettle uses to decide this will
> never succeed, because the RUN rule that called udevsettle is not
> finished). To get the rule to finish processing, the program that RUN
> ran needs to exit. *Then* udevsettle will finish.
yes i see it, but anyway what does the "very short running tasks" means?
my scripts is about a second (under normal circumstances) which is
imho very short from a shell script:-)
> It probably makes the most sense to just make your script run most of
> its logic in the background, instead of the foreground. I'm not sure
> exactly what logic udevd uses, but I think it will work to write a
> wrapper script that just runs your current script in the background:
yes i already solve it, but imho it's not a good habit to call
udevsettle from cryptsetup.
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2008-07-03 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 13:11 udev problem with udevsettle Farkas Levente
2008-07-03 16:52 ` Bryan Kadzban
2008-07-03 17:08 ` Marco d'Itri
2008-07-03 20:54 ` Farkas Levente [this message]
2008-07-03 21:32 ` Bryan Kadzban
2008-07-03 21:49 ` Bryan Kadzban
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486D3C87.4040207@lfarkas.org \
--to=lfarkas@lfarkas.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).