From: Petr Lautrbach <plautrba@redhat.com>
To: Stefan Seyfried <seife@suse.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Add on demand functionality to bluetooth init script
Date: Mon, 08 Jun 2009 13:31:34 +0200 [thread overview]
Message-ID: <4A2CF696.8020702@redhat.com> (raw)
In-Reply-To: <20090605145144.GB7296@suse.de>
On 06/05/2009 04:51 PM, Stefan Seyfried wrote:
> On Thu, Jun 04, 2009 at 04:52:46PM +0200, Petr Lautrbach wrote:
>> Hi.
>>
>> This patch adds on demand functionality for bluetooth service based on udev events.
>> It's adapted from Fedora [1].
>
> JFTR: I'd appreciate if this (or something similar) was added. I have a similar hack in
> the openSUSE package (though not as elaborate as this one), and for consistency across
> distributions, having a solution upstream is preferred.
>
>> Idea is that bluetoothd doesn't need to be running unless the user actually has a bluetooth device.
>
> Just out of interest: how did you solve the "udev event for bluetooth adapter
> fires before dbus is started" probem?
>
"udev event for bluetooth adapter fires before dbus is started" can happend in these cases:
boot process or changing runlevel:
udev is started, dbus is not started yet and somebody inserts bluetooth device ->
udev calls "/etc/init.d/bluetooth start" which fails
but there is running boot (changing runlevel) process, so sometime after starting dbus is started
bluetooth again, this time successfully
running system without dbus:
bluetoothd will not run even without this feature
Regards,
Petr
--
Petr Lautrbach, Red Hat, Inc.
next prev parent reply other threads:[~2009-06-08 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 14:52 [PATCH] Add on demand functionality to bluetooth init script Petr Lautrbach
2009-06-05 14:51 ` Stefan Seyfried
2009-06-08 11:31 ` Petr Lautrbach [this message]
2009-06-08 11:59 ` Stefan Seyfried
2009-06-08 12:17 ` Petr Lautrbach
2009-06-05 15:38 ` Johan Hedberg
2009-06-05 15:48 ` Marcel Holtmann
2009-06-05 16:42 ` Stefan Seyfried
2009-06-05 16:53 ` Stefan Seyfried
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=4A2CF696.8020702@redhat.com \
--to=plautrba@redhat.com \
--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.