From: Marcel Holtmann <marcel@holtmann.org>
To: "Williams, Richard" <Richard.Williams@VITRONICS.com>
Cc: "Bluez-Devel (E-mail)" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BlueZ startup
Date: Tue, 15 Jun 2004 16:58:48 +0200 [thread overview]
Message-ID: <1087311528.13792.92.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A4028BA6@goofy.vitronics.com>
Hi Richard,
> I have a single board computer x-scale processor running Linux 2.4.26. I plan to have several Bluetooth devices and services on my system, such as several rfcomm TTY connections, SDP, OPD, PAND all running simultaneously. I want all the BT drivers and applications to start at boot time.
>
> The question is, in what order should the various bluetooth pieces be started, and when in the boot-up cycle. Currently, I start hcid, sdp and opd in /etc/rc.d/init.d/bluetooth. This seems to work OK. But if I also attempt to start pand from inside /etc/rc.d/init.d/bluetooth I frequently get kernel panics.
>
> How should I start up these services ?
you can start them mostly in any order, but hcid and sdpd should be
first. Show us the kernel panic.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-06-15 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 14:00 [Bluez-devel] BlueZ startup Williams, Richard
2004-06-15 14:58 ` 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=1087311528.13792.92.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Richard.Williams@VITRONICS.com \
--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.