From: Marcel Holtmann <marcel@holtmann.org>
To: "Douglas, William" <william.douglas@intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Correct the dbus service file's systemd unit name for bluez.
Date: Sat, 23 Feb 2013 22:34:39 +0100 [thread overview]
Message-ID: <1361655279.3902.2.camel@aeonflux> (raw)
In-Reply-To: <CABhPDt9cnp=CiE0_U4kBL17WNrktsSrCrOq_Ly-x3+k0e4CKEw@mail.gmail.com>
Hi William,
> >> Even though dbus-org.bluez.service is set as an alias for the
> >> bluetooth.service systemd unit file, systemd will not be able to load
> >> the bluetooth daemon without the daemon being enabled (and the
> >> dbus-org.bluez.service file linked to bluetooth.service). This patch
> >> allows the daemon to be loaded by other services on demand.
> >
> > as you have noticed we have this in bluetooth.service:
> >
> > [Install]
> > WantedBy=bluetooth.target
> > Alias=dbus-org.bluez.service
> >
> > Isn't this exactly what we want anyway. The service must be enabled
> > first before it will ever auto-started. Otherwise it just auto-starts
> > and the user can never get rid of it.
> >
>
> Oh I didn't realize that was the intent. Is that because if it is auto
> enabled there is no way for the service to be masked to avoid it from
> auto starting? I was hoping to have the daemon start once it was
> requested by default. Probably more of a distro choice though.
I am actually curious on what is the best way here. My current thinking
is that the daemon should be started when hardware is present. Starting
it only because of a UI applet seems silly if there is no hardware
present, but I am not sure what's the appropriate default is here.
Regards
Marcel
next prev parent reply other threads:[~2013-02-23 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 18:57 [PATCH] Correct the dbus service file's systemd unit name for bluez William Douglas
2013-02-23 10:48 ` Marcel Holtmann
2013-02-23 18:06 ` Douglas, William
2013-02-23 21:34 ` Marcel Holtmann [this message]
2013-02-24 20:22 ` Douglas, William
2013-02-25 7:54 ` Marcel Holtmann
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=1361655279.3902.2.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=william.douglas@intel.com \
/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