Hi, pe, 2025-04-18 kello 16:30 +0100, Andrew Sayers kirjoitti: > Obex is a device-oriented protocol, so only one instance can run per device. > But Linux file security is user-oriented, so obexd should be a user service. > Tell systemd to only run this service for the first non-system user to log in. Sound servers have this same problem. As there's no concept of multiple users in BlueZ, the solution there is to monitor systemd/elogind seat state, and detach the user process from bluetoothd if the seat is inactive. How to do the monitoring, see: https://gitlab.freedesktop.org/pipewire/wireplumber/-/blob/master/modules/module-logind.c#L52 > > This series causes systemd not to run obexd if it would just generate errors, > after adding a new bluez.tmpfiles file that distributors will need to install. > > Signed-off-by: Andrew Sayers <kernel.org@xxxxxxxxxxxxxxx> > --- > > V1 -> V2 add a hint in obex.service.in about installing the tmpfile > (recommended by Luiz Augusto von Dentz) > > Andrew Sayers (2): > build: add bluez.tmpfiles > obexd: only run one instance at once > > .gitignore | 1 + > configure.ac | 1 + > obexd/src/obex.service.in | 9 +++++++++ > tools/bluez.tmpfiles.in | 1 + > 4 files changed, 12 insertions(+)
