From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Should hcid wait for dbus daemon?
Date: Mon, 15 Jan 2007 14:30:26 +0100 [thread overview]
Message-ID: <1168867826.5728.14.camel@violet> (raw)
In-Reply-To: <200701081837.04388.dgollub@suse.de>
Hi Daniel,
> the hcid daemon aborts when there is no dbus daemon running. What about
> enhancing hcid to handle the case that the dbus daemon get started after
> hcid. I know there are might be not many use cases. But at least i know one
> case ;)
>
> To avoid that there is another "unneeded" service running, i want to call only
> the bluetooth init scripts when there is a bluetooth device plugged in. This
> is done by a simple udev rule, which calls the bluetooth init script when the
> device got plugged in.
>
> So there is no need to insserv or do any other stuff like running YaST or
> something like that. Just turn on the bluetooth device or plug it in and the
> bluetooth service get started by udev.
>
> The only problem is during boot. udev get started before the dbus daemon, and
> will trigger the udev rule which calls the bluetooth init script. Then hcid
> will fail because the dbus daemon isn't started in this early stage of boot.
>
> If the hcid would wait for the dbus daemon this wouldn't be a problem. At
> least hcid can handle a dbus daemon restart, maybe we can enhance this.
>
> I know this can be also done in the bluetooth init script, but maybe someone
> else insist on this enhancement.
I don't think that it is a good idea to have udev start daemons. My
understanding is that udev is for creating device nodes or init
hardware. In case of BlueZ it must start a number of daemons to have a
fully working Bluetooth setup. This task is better done by systems like
upstart which handle dependencies.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-01-15 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 17:37 [Bluez-devel] Should hcid wait for dbus daemon? Daniel Gollub
2007-01-08 18:47 ` Johan Hedberg
2007-01-08 23:31 ` Luca Capello
2007-01-09 0:01 ` Daniel Gollub
2007-01-09 8:27 ` Stefan Seyfried
2007-01-08 23:41 ` Daniel Gollub
2007-01-12 15:25 ` Stefan Seyfried
2007-01-13 17:39 ` Andrey Rahmatullin
2007-01-15 13:30 ` Marcel Holtmann [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=1168867826.5728.14.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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.