From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevsend fallback
Date: Fri, 14 May 2004 22:21:03 +0000 [thread overview]
Message-ID: <20040514222103.GD16180@kroah.com> (raw)
In-Reply-To: <20040511111641.GB12034@vrfy.org>
On Fri, May 14, 2004 at 01:22:06PM +0200, Kay Sievers wrote:
> On Tue, May 11, 2004 at 04:54:44PM -0700, Greg KH wrote:
> > On Tue, May 11, 2004 at 01:16:41PM +0200, Kay Sievers wrote:
> > > 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?
> >
> > That sounds like a good "failsafe" thing to do.
>
> Here we go:
>
> Add a fallback udev call to udevsend. If udev is unable to send the
> event to udevd, we call the udevd binary instead of do nothing and exit.
Applied, thanks.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-05-14 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 11:16 udevsend fallback Kay Sievers
2004-05-11 12:21 ` 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 [this message]
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=20040514222103.GD16180@kroah.com \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.