On 06/13/2009 12:43 AM, Bastien Nocera wrote:
On Fri, 2009-06-12 at 23:59 +0530, Rahul Sundaram wrote:
On 06/12/2009 11:35 PM, Bastien Nocera wrote:
Heya,
I've added a patch to bluetoothd in F-12 to support being started via
udev, on-demand. bluetoothd will now only start up when you have a
Heya,
I've added a patch to bluetoothd in F-12 to support being started via
udev, on-demand. bluetoothd will now only start up when you have a
Bluetooth adapter plugged, and will exit 30 seconds after the last one
went away.
The only purpose of the bluetooth initscript is now to switch HID proxy
On Fri, Jun 12, 2009 at 07:05:39PM +0100, Bastien Nocera wrote:
I've added a patch to bluetoothd in F-12 to support being started via
udev, on-demand. bluetoothd will now only start up when you have a
Bluetooth adapter plugged, and will exit 30 seconds after the last one
went away.
The only
On Fri, Jun 12, 2009 at 8:11 PM, Kyle McMartink...@mcmartin.ca wrote:
On Fri, Jun 12, 2009 at 07:05:39PM +0100, Bastien Nocera wrote:
I've added a patch to bluetoothd in F-12 to support being started via
udev, on-demand. bluetoothd will now only start up when you have a
Bluetooth adapter
On Fri, 2009-06-12 at 20:20 +0200, drago01 wrote:
On Fri, Jun 12, 2009 at 8:11 PM, Kyle McMartink...@mcmartin.ca wrote:
On Fri, Jun 12, 2009 at 07:05:39PM +0100, Bastien Nocera wrote:
I've added a patch to bluetoothd in F-12 to support being started via
udev, on-demand. bluetoothd will now
On Fri, Jun 12, 2009 at 8:27 PM, Bastien Nocerabnoc...@redhat.com wrote:
On Fri, 2009-06-12 at 20:20 +0200, drago01 wrote:
On Fri, Jun 12, 2009 at 8:11 PM, Kyle McMartink...@mcmartin.ca wrote:
On Fri, Jun 12, 2009 at 07:05:39PM +0100, Bastien Nocera wrote:
I've added a patch to bluetoothd in
On 06/12/2009 11:35 PM, Bastien Nocera wrote:
Heya,
I've added a patch to bluetoothd in F-12 to support being started via
udev, on-demand. bluetoothd will now only start up when you have a
Bluetooth adapter plugged, and will exit 30 seconds after the last one
went away.
Can you add these
On Fri, 12.06.09 19:26, Bastien Nocera (bnoc...@redhat.com) wrote:
Every time there's an add action for a Bluetooth device, udev will run
bluetoothd --udev.
bluetoothd will fail with an error if D-Bus isn't started (on bootup),
and the udev coldplug (done in udev-post) will run the rule
On Fri, 2009-06-12 at 14:39 -0400, Colin Walters wrote:
On Fri, Jun 12, 2009 at 2:26 PM, Bastien Nocerabnoc...@redhat.com wrote:
bluetoothd will exit itself after 30 seconds when no adapters are
present. There's a potential race if the udev add event happens in
between the time the time
On Fri, 12.06.09 20:10, Bastien Nocera (bnoc...@redhat.com) wrote:
This could be fixed by first releasing the service name synchronously,
then processing all queued requests and only then closing/exiting.
Hmm, will bluetoothd also be started via bus activation? If so, it
wuld probably
10 matches
Mail list logo
