All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: Bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Only one pand-daemon?
Date: Mon, 02 Jul 2007 23:49:07 +0200	[thread overview]
Message-ID: <1183412947.20815.7.camel@localhost> (raw)

Hello all,

I am facing the problem that I cannot start more than
one listening pand-daemon, in spite of using two usb-dongles.
The second call with 'pand --listen -e bdaddr ...' immediately
ends with return value zero and no traces in any log file.
I am running Bluez-utils 3.7 on Debian Etch. Slowly I am 
beginning to think that it could be DBUS that haunts me, but I
have just begun studying the source code of pand to make sure.
Any pointers are welcome.!


Best regards,	Mats Erik Andersson


-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-07-02 21:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 21:49 Mats Erik Andersson [this message]
2007-07-03  3:33 ` [Bluez-users] Only one pand-daemon? Marcel Holtmann
2007-07-03 11:39   ` Mats Erik Andersson
2007-07-04  1:48     ` Marcel Holtmann
2007-07-04 13:43       ` [Bluez-users] dbus problem, Was: " Mats Erik Andersson
2007-07-05  8:10         ` Marcel Holtmann
2007-07-06  9:53           ` [Bluez-users] dbus problem for pand service Mats Erik Andersson
2007-07-11  9:54             ` 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=1183412947.20815.7.camel@localhost \
    --to=mats.andersson64@comhem.se \
    --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 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.