Enable D-Bus activation of bluetooth.service
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | org.bluez.service: enable D-Bus activation of bluetooth.servicesrc/ | +1 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH BlueZ 0/1] Enable D-Bus activation of bluetooth.service
D-Bus can automatically launch programs on demand when a message is sent to their bus name. Bluez provides src/org.bluez.service for this purpose, but it writes "dbus-org.bluez.service" for the Systemd service name, while the Systemd service is actually named bluetooth.service (generated from src/bluetooth.service.in). The Systemd service defines an alias named dbus-org.bluez.service, but Systemd aliases only come into effect once a unit is enabled.
Effectively, this means that instead of launching bluetoothd on demand whenever it's requested, D-Bus activation is only used if the service is enabled but happens to not be running, such as the first time it's enabled or if it crashes.
Grant Moyer (1):
org.bluez.service: enable D-Bus activation of bluetooth.service
src/org.bluez.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
base-commit: 61a2b3d93897b04fb921a4fb229c0831d13807a8
Signature · 1 line
2.55.0