6 Jul
2010
6 Jul
'10
11:06 a.m.
On Tue, Jul 6, 2010 at 12:51 AM, Geoffrey Mimano <soyfactor@gmail.com> wrote:
gksu rfcomm connect 0 0B:D4:91:39:66:01
They are not matching because the jvm invokes its own shell starts up rfcomm and returns and I am guessing this rfcomm command runs 'headless' in the main os shell. so what you need to do is get the process id of the running rfcomm : the output of this shell command should give you the real process id of the rfcomm process . "ps ax | grep 'rfcomm' | awk '{print $1}' " which you can then you to send a kill signal...