From: Andrew Sayers <kernel.org@pileofstuff.org>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, pav@iki.fi,
Andrew Sayers <kernel.org@pileofstuff.org>
Subject: [PATCH BlueZ v5 6/6] Revert "obexd: only run one instance at once"
Date: Tue, 29 Apr 2025 15:14:16 +0100 [thread overview]
Message-ID: <20250429141533.803295-7-kernel.org@pileofstuff.org> (raw)
In-Reply-To: <20250429141533.803295-1-kernel.org@pileofstuff.org>
No longer needed now services can share resources.
This reverts commit 8d472b8758dcdd89bf13cf2fb06a8846e1f483a0.
Signed-off-by: Andrew Sayers <kernel.org@pileofstuff.org>
---
obexd/src/obex.service.in | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/obexd/src/obex.service.in b/obexd/src/obex.service.in
index f269bc513..cf4d8c985 100644
--- a/obexd/src/obex.service.in
+++ b/obexd/src/obex.service.in
@@ -1,19 +1,10 @@
[Unit]
Description=Bluetooth OBEX service
-# This is a user-specific service, but bluetooth is a device-specific protocol.
-# Only run one instance at a time, even if multiple users log in at once:
-ConditionPathExists=!/run/lock/bluez/obexd.lock
-ConditionUser=!@system
[Service]
Type=dbus
BusName=org.bluez.obex
ExecStart=@PKGLIBEXECDIR@/obexd
-# If the service fails on the following line, please ensure
-# the bluez tmpfile has been installed in /usr/lib/tmpfiles.d/
-ExecStartPre=touch /run/lock/bluez/obexd.lock
-ExecStopPost=rm -f /run/lock/bluez/obexd.lock
-
[Install]
Alias=dbus-org.bluez.obex.service
--
2.49.0
next prev parent reply other threads:[~2025-04-29 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 14:14 [PATCH BlueZ v5 0/6] obexd: unregister profiles when the user is inactive Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 1/6] pbap: Support calling pbap_init() after pbap_exit() Andrew Sayers
2025-04-29 15:51 ` obexd: unregister profiles when the user is inactive bluez.test.bot
2025-04-29 14:14 ` [PATCH BlueZ v5 2/6] obexd/bluetooth: Support calling bluetooth_init() after bluetooth_exit() Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 3/6] obexd: Support creating private system/session bus connections Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 4/6] obexd: Unregister profiles when the user is inactive Andrew Sayers
2025-04-29 17:25 ` Luiz Augusto von Dentz
2025-04-29 19:20 ` Andrew Sayers
2025-04-29 21:12 ` Luiz Augusto von Dentz
2025-04-29 14:14 ` [PATCH BlueZ v5 5/6] obexd: Support sd_login_monitor_get_timeout() Andrew Sayers
2025-04-29 14:14 ` Andrew Sayers [this message]
2025-04-29 18:10 ` [PATCH BlueZ v5 0/6] obexd: unregister profiles when the user is inactive patchwork-bot+bluetooth
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=20250429141533.803295-7-kernel.org@pileofstuff.org \
--to=kernel.org@pileofstuff.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pav@iki.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox