From: Trejkaz Xaoza <trejkaz@trypticon.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Device class resetting itself after device is removed
Date: Tue, 2 Nov 2004 00:56:00 +1100 [thread overview]
Message-ID: <200411020056.00919.trejkaz@trypticon.org> (raw)
In-Reply-To: <1099313117.16247.84.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On Mon, 1 Nov 2004 23:45, Marcel Holtmann wrote:
>
> are you sure that your hcid is running?
Yup, looks healthy so far:
[100] trejkaz@raven:~> ps -ef|grep hcid
root 6821 1 0 Nov01 ? 00:00:00 hcid: processing events
TX
--
Email: Trejkaz Xaoza <trejkaz@xaoza.net>
Web site: http://xaoza.net/
Jabber ID: trejkaz@jabber.xaoza.net
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-01 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 11:22 [Bluez-users] Device class resetting itself after device is removed Trejkaz Xaoza
2004-11-01 12:45 ` Marcel Holtmann
2004-11-01 13:56 ` Trejkaz Xaoza [this message]
2004-11-01 14:33 ` 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=200411020056.00919.trejkaz@trypticon.org \
--to=trejkaz@trypticon.org \
--cc=bluez-users@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