All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Till Dörges" <lists@doerges.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid.conf: device section with specific	bt	address is ignored
Date: Sun, 20 May 2007 18:42:33 +0200	[thread overview]
Message-ID: <46507A79.5010409@doerges.net> (raw)
In-Reply-To: <1179674825.23757.12.camel@violet>

Hi Marcel,

Am 20.05.2007 17:27, Marcel Holtmann schrieb:

>> in hcid.conf a device section with a bluetooth address specified apparently is
>> ignored. The following should work according to the man-page:
>>
>>> # *not* working
>>> device 00:09:DD:10:42:C4 {
>>>        name "%h (dongle 1)";
>>> [...]
>> The default device section is working as expected.
> 
> should be solved with bluez-utils-3.10.1.

That's nice to hear. :-)

Then out of curiosity: For bluez-utils-3.10.1 I get this for hcid:

--- snip ---
May 19 18:33:38 myhost hcid[1942]: Can't open system message bus connection: Failed
to connect to socket /var/run/ dbus/system_bus_socket: No such file or directory
May 19 18:33:38 myhost hcid[1942]: Unable to get on D-Bus
--- snip ---

Was there a dbus related change? Or is it due to a missing bluez-hcid.conf file
(present in 3.7 but not in 3.10.1)?

Thanks -- Till

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-05-20 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20 14:22 [Bluez-devel] hcid.conf: device section with specific bt address is ignored Till Dörges
2007-05-20 15:27 ` Marcel Holtmann
2007-05-20 16:42   ` Till Dörges [this message]
2007-05-20 16:56     ` 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=46507A79.5010409@doerges.net \
    --to=lists@doerges.net \
    --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.