From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid.conf options not honored after DBus API had been used?
Date: Tue, 19 Dec 2006 17:36:14 +0100 [thread overview]
Message-ID: <20061219163614.GM7959@suse.de> (raw)
In-Reply-To: <1166544053.7309.7.camel@violet>
Hi Marcel,
On Tue, Dec 19, 2006 at 05:00:53PM +0100, Marcel Holtmann wrote:
=
> > Any opinions? How is this handled on other distributions?
> =
> once you have values set through the D-Bus API they have priority and
> that is the only possible choice. The provided configuration options in
> hcid.conf are only default values for the distributions. No user should
> ever modify these values. This also means that YaST should no longer
> modify hcid.conf. Simply call the appropriate method via dbus-send.
Ok. How about shipping an empty hcid.conf with bluez-utils (or maybe
list the options, but comment them out) so everybody knows that "if you
touch anything here, you better know what you are doing"?
> In general you can have as many configuration tools as you want. The
> only small thing you need to take care of is to listen to signals for
> your settings, because another tool might change a value while you are
> running.
Yes, or just make all those dbus-send calls at once before exiting :-)
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-19 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 15:51 [Bluez-devel] hcid.conf options not honored after DBus API had been used? Stefan Seyfried
2006-12-19 16:00 ` Marcel Holtmann
2006-12-19 16:36 ` Stefan Seyfried [this message]
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=20061219163614.GM7959@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@lists.sourceforge.net \
/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.