Re: listening socket not notified when bluetoothd stops, but becomes unusable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Jan 5, 2011 at 1:48 PM, Ilya Basin <basinilya@xxxxxxxxx> wrote:
> I use nonblocking sockets and select(). When I restart bluetoothd,
> select() doen't return, but the listening socket won't accept
> connections anymore. How to handle this correctly?

If you are using BDADDR_ANY than that is probably ok, now for specific
adapter this could be a bug but Im not sure about the powered state
before you restart and if RememberPowered is set, it could be that the
adapter is powered off after bluetoothd restart than you won't be able
to accept connections.

-- 
Luiz Augusto von Dentz
Computer Engineer
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux