All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: Stefan Seyfried <seife@suse.de>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Add udev mode to bluetoothd
Date: Fri, 12 Jun 2009 17:28:18 +0200	[thread overview]
Message-ID: <1244820498.5536.7.camel@violet> (raw)
In-Reply-To: <1244796020.3280.13.camel@snoogens.fab.redhat.com>

Hi Bastien,

> > >> As discussed on IRC.
> > >>
> > >> Still needed:
> > >> - patch to wait for the bus to startup in udev mode
> > 
> > Should we really do that? (What if the bus never appears?, how long should we
> > wait?)
> > The alternative (not overwhelmingly nice, I admit) would be to record
> > somewhere in the system that bluetoothd tried to start but could not due to
> > the missing bus and then start it "manually" by an init script that is
> > guaranteed to run after DBus is started.
> 
> Under normal conditions, we'd exit(1) if started and the bus isn't
> available, and udev would pick that up, marking our job as failed, and
> relaunching us later in the boot process, under coldplug.
> 
> Marcel didn't like the idea though.

so how does udev handle this exactly. We try bluetoothd and it fails,
then it tries again later? What time exactly? How often? Does this
affect the fast-boot effort?

Regards

Marcel



  reply	other threads:[~2009-06-12 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 17:38 [PATCH] Add udev mode to bluetoothd Bastien Nocera
2009-06-11 17:50 ` Marcel Holtmann
2009-06-12  7:40   ` Stefan Seyfried
2009-06-12  8:28     ` Stefan Seyfried
2009-06-12 17:43       ` Bastien Nocera
2009-06-12  8:40     ` Bastien Nocera
2009-06-12 15:28       ` Marcel Holtmann [this message]
2009-06-12 17:58         ` Bastien Nocera
2009-06-13 19:51           ` Marcel Holtmann

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=1244820498.5536.7.camel@violet \
    --to=marcel@holtmann.org \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=seife@suse.de \
    /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.