* FTP problem during obexd initialization?
@ 2010-05-12 21:28 Daniel Abraham
2010-05-13 7:02 ` Simon
0 siblings, 1 reply; 2+ messages in thread
From: Daniel Abraham @ 2010-05-12 21:28 UTC (permalink / raw)
To: linux-bluetooth
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: FTP problem during obexd initialization?
2010-05-12 21:28 FTP problem during obexd initialization? Daniel Abraham
@ 2010-05-13 7:02 ` Simon
0 siblings, 0 replies; 2+ messages in thread
From: Simon @ 2010-05-13 7:02 UTC (permalink / raw)
To: linux-bluetooth
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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-05-13 7:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-12 21:28 FTP problem during obexd initialization? Daniel Abraham
2010-05-13 7:02 ` Simon
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).