From: Achim Bohnet <ach@mpe.mpg.de>
To: bluez-devel@lists.sourceforge.net
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@nokia.com>
Subject: Re: [Bluez-devel] D-BUS fixes for hcid
Date: Wed, 16 Jun 2004 15:58:56 +0200 [thread overview]
Message-ID: <200406161558.56578.ach@mpe.mpg.de> (raw)
In-Reply-To: <1087391183.4309.13.camel@pegasus>
On Wednesday 16 June 2004 15:06, Marcel Holtmann wrote:
> Hi Johan,
>
> > 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.
Agreed.
> if we change it this way, then how do the D-Bus PIN Helper get its
> information about the running X server?
On debian, dbus-1-utils installs a xsession startup script
that checks for use-session-dbus in /etc/X11/Xsession.options
Therefore dbus daemon knows the $DISPLAY.
Johan: When 2 xservers are running on vt7 as :0 and vt8 as :1
respectively. Do the 2 dbus daemons know which one is active?
(i.e. crt or lcd currently displays :0 or :1) Would be nice to
get the pin helper window on :1 if one is working there instead
of on :0 ;)
Achim
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
--
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- reddy@lion.austin.ibm.com
next prev parent reply other threads:[~2004-06-16 13:58 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
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 [this message]
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=200406161558.56578.ach@mpe.mpg.de \
--to=ach@mpe.mpg.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=johan.hedberg@nokia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox