From: Johan Hedberg <johan.hedberg@nokia.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] D-BUS fixes for hcid
Date: Wed, 16 Jun 2004 15:45:41 +0300 [thread overview]
Message-ID: <20040616124541.GA8629@kone> (raw)
In-Reply-To: <1087388298.4309.10.camel@pegasus>
Hi Marcel,
I must admit that I hadn't looked into how the bluez-pin program works
in D-BUS mode. It seems it should be running all the time to be able to
receive any D-BUS requests, correct?
The service activation feature of D-BUS which I have talked about is
designed to solve the problem where some D-BUS service should be
launched on-demand. I think the pin-helper falls exactly into this
category, and would be IMHO more elegant if it wouldn't have to be
running all the time but would be automatically launched by D-BUS daemon
when needed.
On Wed, Jun 16, 2004, ext Marcel Holtmann wrote:
> > The second part (dbus_message_set_auto_activation) enables service
> > activation if the PinAgent service isn't aquired by any process (i.e.
> > the D-BUS daemon will execute the pin-helper program if needed).
>
> The hcid shouldn't execute the D-Bus PIN helper.
Not hcid, but the D-BUS daemon.
> From my local .xession I start "bluez-pin --dbus &" and everything works
> fine.
Ok. But by using D-BUS service activation, you wouldn't need to do this.
Johan
next prev parent reply other threads:[~2004-06-16 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 11:27 [Bluez-devel] D-BUS fixes for hcid Johan Hedberg
2004-06-16 11:37 ` Marcel Holtmann
2004-06-16 11:57 ` Johan Hedberg
2004-06-16 12:05 ` Johan Hedberg
2004-06-16 12:18 ` Marcel Holtmann
2004-06-16 12:45 ` Johan Hedberg [this message]
2004-06-16 13:06 ` Marcel Holtmann
2004-06-16 13:46 ` Johan Hedberg
2004-06-16 13:53 ` Marcel Holtmann
2004-06-16 13:58 ` Achim Bohnet
2004-06-16 14:18 ` Johan Hedberg
2004-06-16 23:06 ` Marcel Holtmann
2004-06-17 9:48 ` Johan Hedberg
2004-06-17 12:05 ` Marcel Holtmann
2004-06-17 7:27 ` Sjoerd Simons
2004-06-18 7:30 ` Achim Bohnet
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=20040616124541.GA8629@kone \
--to=johan.hedberg@nokia.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.