From: Edd Dumbill <edd@usefulinc.com>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] hcid dying
Date: Mon, 21 Jun 2004 12:31:44 +0100 [thread overview]
Message-ID: <1087817504.10134.16.camel@saag> (raw)
Recently I've experienced the hcid process dying without warning. I've
not yet been able to isolate why this happens, but another user reported
the same thing happening to me today, so I thought I'd ask if anybody
else was seeing this happen.
-- Edd
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-06-21 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 11:31 Edd Dumbill [this message]
2004-06-21 11:44 ` [Bluez-users] hcid dying Marcel Holtmann
2004-06-21 12:04 ` Edd Dumbill
2004-06-21 12:30 ` 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=1087817504.10134.16.camel@saag \
--to=edd@usefulinc.com \
--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