Re: Bluetooth wireless activity triggers udev rule

[Aras Vaichas <arasv@magtech.com.au>]

Sujit Karataparambil wrote:
> On Wed, Aug 13, 2008 at 9:34 AM, Aras Vaichas <arasv@magtech.com.au> wrote:
>   
>> Hi, I'm currently integrating runit and udev. I have a udev rule which
>> runs my Blue-Z startup scripts when I plug in the USB BT dongle:
>>
>> ACTION="add", ENV{SUBSYSTEM}="bluetooth", RUN+="/usr/bin/sv up bluetooth"
>>
>>     
>
> Which is the bluetooth  connectivity that  this USB  device is plugging to.
>
>   
>> This works really well, cold plugging, etc. No problems.
>>
>> I've found an interesting quirk though. Here is the sequence of events:
>>     
>
> Here again ??  Bluetooth ??
>   
>> Computer A: I start up my system with the BT dongle inserted, the Blue-Z
>> scripts are started via udev coldplugging script
>> Computer B: I set up a task which searches for BT devices and tries to
>> form a PPP connection
>> Computer B: Detects the BT dongle on Computer A, records the address and
>> forms a PPP connection
>>     
>
> PPP With Bluetooth ???
>
>   
>> Computer A: I disable the Blue-Z scripts # sv down bluetooth
>> Computer B: Attempts to connect to A again, and sends a BT signal to
>> connect ...
>> Computer A: The BT dongle sends a wireless wakeup (wake-on-lan?) signal
>> which causes udev to run the Blue-Z utils startup script again ...
>>     
>
> Bluetooth ?? PPP ???
Sorry, but I do not understand  what you are asking here. Can you please
write in proper sentences?

Aras

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________