rpm/bluez
SHA256
1
0
Fork 0
forked from pool/bluez
Code Pull Requests Activity

OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=38

Browse Source
This commit is contained in:
OBS User unknown
2009-07-10 14:41:47 +00:00
committed by Git OBS Bridge
parent 6d49778031
commit 56ab2d814e
15 changed files with 137 additions and 443 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.SUSE
View File

@@ -3,21 +3,13 @@ Notes about the SUSE bluez packages:
How does bluetoothd get started?
--------------------------------
Bluetoothd is started via D-Bus activation. This means: as soon as somebody
is requesting bluez services via D-Bus, bluetoothd is started.
Additionally, there is a udev rule that runs /lib/udev/bluetooth.sh every
time a bluetooth device is plugged into the system. This script sends a
request via dbus-send to start the bluetoothd.
Bluetoothd is started via udev. This means: as soon as a bluetooth device
is inserted, bluetoothd is started with the option "--udev".
For the case that D-Bus is not yet running during system bootup when the
adapter is detected, the script creates /dev/shm/bluetooth-adapter-present/
which is used in a later init script /etc/init.d/bluetooth-coldplug to
decide if bluetooth services should be started or not.
Of course you can still decide to always start bluetoothd on every boot by
issuing the "insserv bluetooth" command or enabling it with the YaST2 runlevel
editor.
adapter is detected, bluetoothd will quit with exit code 1, udev will notice
that and then try to restart bluetoothd later.
If you want to prevent starting of the bluetooth service, edit
/etc/sysconfig/bluetooth and set START_SERVICES to "no".
/etc/sysconfig/bluetooth and set START_BLUETOOTHD to "no".
Have a lot of fun...