Hi John, On Thu, Dec 14, 2017 at 1:35 PM, Szymon Janc <szymon.janc@xxxxxxxxxxx> wrote: > Hi John, > > On Thursday, 14 December 2017 16:21:32 CET John Klug wrote: >> What is holding the connection open is bluetoothd. >> >> After closing the file descriptor for RFCOMM, there are two file >> descriptors in the Bluetooth daemon that are left: >> >> bluetooth 1406 root 18u sock 0,7 0t0 26587 protocol: >> RFCOMM bluetooth 1406 root 19u sock 0,7 0t0 26602 >> protocol: RFCOMM >> >> By terminating the application these go away, but what if I wish to >> keep the daemon running? How do I tell the Bluetooth daemon to close >> the RFCOMM sockets? > > I think you need to shutdown() socket. Yep, shutdown must be used since bluetoothd keeps a reference in case it has to disconnect and to keep track of the service state. We should perhaps document that we expect the user application to shutdown the fd in case it want it to be disconnected. -- Luiz Augusto von Dentz -- 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
