[Xastir] Best of Both Worlds

[Keith Kaiser]

I've been playing with this for a couple of hours now and here is what I learned.

If I start MacTNC first, I can't run Xastir, with the TNC even after quitting MacTNC.
If I reboot then start Xastir it sees and hears the TNC just fine.

If I try to bring up MacTNC at the same time Xastir is up I get a 'Unable to open Port' error. No surprise, since they would both be trying to use the same port.

If I quit Xastir, then launch MacTNC everything works great. 

I'm guessing Xastir is playing nice and releasing its resources when its quit. But not so for MacTNC because Xastir can't find the port after MacTNC quits.

Any thoughts here?

On Jan 13, 2010, at 5:13 PM, Curt, WE7U wrote:

> On Wed, 13 Jan 2010, Keith Kaiser wrote:
> 
>> I also want to be able to use this setup with Xastir. To do this I
>> turn off MacTNC (the terminal program) and launch Xastir. It comes
>> up and I go to the 'Interface Control' and select the appropriate
>> device. This device uses the "tnc-startup.kpc3" script. But it
>> doesn't work. The TNC is not seen by Xastir, no packets come in as
>> seen via the 'Display Packet Data' under the 'View' menu.
>> 
>> Trying to turn it off again via the 'Interface Control' locks up
>> Xastir to the point where I have to force quit the X11 application
>> to get out of it. Then I have to delete the pid in order to start
>> the entire process over again.
>> 
>> Yes, I'm sure I have the correct port set in the 'Interface
>> Control', the exact same one used by MacTNC.
> 
> I hate to get all "Unixy" on you, but have you looked at the
> permissions and ownership/group ownership for the device you're
> trying to open?
> 
> Also, have you tried starting Xastir from inside an Xterm or
> equivalent?  I'll bet Xastir is emitting error messages but you're
> not seeing them because you're starting Xastir graphically.
> 
> More than likely it's a permission/ownership problem.  The "normal"
> solution is to do an "ls -l" in the directory where the device
> resides to see the group ownership, then add yourself to the group
> that owns the device.  After that, log out, log back in to gain
> those permissions, then see if Xastir can open the device.
> 
> If that fails, there are other methods, such as changing the
> permission on the device, or setting Xastir SUID Root.
> 
> -- 
> Curt, WE7U.                         <http://www.eskimo.com/~archer>
>   APRS:  Where it's at!                    <http://www.xastir.org>
>  Lotto:  A tax on people who are bad at math. - unknown
> Windows:  Microsoft's tax on computer illiterates. - WE7U.
> The world DOES revolve around me:  I picked the coordinate system!"
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir