From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] save_link_key in 2.19
Date: Tue, 16 Aug 2005 17:32:22 +0200 [thread overview]
Message-ID: <1124206342.7466.14.camel@pegasus> (raw)
In-Reply-To: <200508112219.12677.adam.cooper@port.ac.uk>
Hi Adam,
> I've just spent the last couple of hours trying to figure out why my 'hcid'
> was not storing my paired devices between restarts. I'm running gentoo and
> the latest version of bluez utils (2.19).
>
> In a final act of desperation I had a good hunt through the code. Low and
> behold the 'save_link_key' function has been commented out, along with the
> calls to it.
>
> Is there a specific reason this is so?
>
> My mobile runs with it's visibility off so not being able to save pairings is
> a bit of a pain.
the newer hcid stores the link keys under /var/lib/bluetooth/. Check if
you see a directory with your BD_ADDR there.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-16 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 22:19 [Bluez-devel] save_link_key in 2.19 Adam Cooper
2005-08-16 15:32 ` Marcel Holtmann [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=1124206342.7466.14.camel@pegasus \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox