Re: [Bluez-devel] starting order in debian init script for bluez

[Marcel Holtmann <marcel@holtmann.org>]

Hi Matthias,

> I noticed that in /etc/init.d/bluez-utils from bluez-utils 2.7-4, the 
> hcd2hci command is executed after starting all other bluez stuff:
> 
> case "$1" in
>    start)
>          echo -n "Starting $DESC:"
>          start-stop-daemon --start --quiet --exec $HCID || true
>          echo -n " $HCID_NAME"
>          start_uarts || true
>          start_rfcomm || true
>          start-stop-daemon --start --quiet --exec $SDPD || true
>          echo -n " $SDPD_NAME"
>          start_pan || true
>          start_hid || true
>          echo "."
>          enable_hci_input || true
>          ;;
> 
> Wouldn't it be better to start it before rfcomm/sdpd/pand/hidd, to allow 
> these services to use the dongle immediately?

no, because the hcid/sdpd/rfcomm/pand/hidd etc. can be started without
any real device attached. And when you run hid2hci to switch into HCI
mode, the hidd must already running to accept the reconnect from your
HID devices.

> I had a problem connection a Logitech-Hub-dongled PC to a NAP, and 
> changing the order (and adding 'sleep 2' before start_pan, but that's a 
> different story I guess) helped here.

If you start a client connection then this is really a different story.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel