From: Marcel Holtmann <marcel@holtmann.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid hotplug initialisation?
Date: Mon, 09 Feb 2004 11:47:21 +0100 [thread overview]
Message-ID: <1076323641.6869.98.camel@pegasus> (raw)
In-Reply-To: <1076323204.5263.34.camel@kalkyl.roxen.com>
Hi Fredrik,
> Regarding hcid initilisation, what about having the hotplug stuff
> starting hcid instead of /etc/init.d/hcid?
>
> That way hcid can be installed without using cpu/memory resources
> and it will work automatically when a user inserts some Bluetooth
> device.
no. The bluetooth.agent is only for device specific configuration and
not for starting a deamon. However hcid watches all interfaces and
bluetooth.agent would be called for every device. Multiple running
hcid's will mess up the security manager.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-09 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 10:40 [Bluez-devel] hcid hotplug initialisation? Fredrik Noring
2004-02-09 10:47 ` Marcel Holtmann [this message]
2004-02-09 10:56 ` Fredrik Noring
2004-02-09 11:20 ` Marcel Holtmann
2004-02-09 12:35 ` Fredrik Noring
2004-02-09 12:50 ` Marcel Holtmann
2004-02-09 13:06 ` Fredrik Noring
2004-02-09 15:34 ` 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=1076323641.6869.98.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=noring@nocrew.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.