From: Simon <simonchan1979@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: FTP problem during obexd initialization?
Date: Thu, 13 May 2010 15:02:09 +0800 [thread overview]
Message-ID: <AANLkTimlmVEbjcc79zqkQmOcr8_kU7P2QBGROjBaZxUI@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiklu7yRsbmNbOgSW2b4LobLlguxnJxxMpi_k_sp@mail.gmail.com>
Most probably some other obex instance has occupied the same address,
eg. obex-data-server.
Thanks！
2010/5/13 Daniel Abraham <daniel.shrugged@gmail.com>:
> Whenever I start obexd 0.23 (on Fedora 12 with BlueZ 4.64) with the -f
> argument (FTP), I see the following log message:
>
> "obexd[...]: Bluetooth server register failed: rfcomm_bind: Address
> already in use (98)"
>
> happens only with FTP, and regardless whether I specify other
> protocols (e.g. e/o/p/s).
>
> Is that indicative or a real problem, or just a harmless log message?
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2010-05-13 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 21:28 FTP problem during obexd initialization? Daniel Abraham
2010-05-13 7:02 ` Simon [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=AANLkTimlmVEbjcc79zqkQmOcr8_kU7P2QBGROjBaZxUI@mail.gmail.com \
--to=simonchan1979@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).