From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: udevsend fallback
Date: Tue, 11 May 2004 11:16:41 +0000 [thread overview]
Message-ID: <20040511111641.GB12034@vrfy.org> (raw)
Hi,
the execution of udev depends on the proper fuction of udevd, the
serializing daemon. If we can't connect to udevd within a 20 second we
give up and the request to create a node is lost. Hope this never happens,
but a broken udevd may prevent udev from working.
What do you think? Should we call the udev binary directly from udevsend
instead of discarding the event? This way we would create the node, regardless
of the state of udevd. It would be 20 seconds later and maybe not in the right
sequence order - but the node will propably be there.
Does it sound sane? What do you think?
thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-05-11 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 11:16 Kay Sievers [this message]
2004-05-11 12:21 ` udevsend fallback Harald Hoyer
2004-05-11 23:54 ` Greg KH
2004-05-13 7:51 ` Harald Hoyer
2004-05-13 10:10 ` Kay Sievers
2004-05-13 21:03 ` Greg KH
2004-05-14 11:22 ` Kay Sievers
2004-05-14 22:21 ` Greg KH
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=20040511111641.GB12034@vrfy.org \
--to=kay.sievers@vrfy.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).