That did it Tom, thank you so much for the help and quick response.

73's.

On Oct 28, 2008, at 10:55 AM, Tom Russo wrote:

On Tue, Oct 28, 2008 at 10:41:33AM -0500, we recorded a bogon- computron collision of the <[EMAIL PROTECTED]> flavor, containing:
I have a definition in my Interface Control set up to talk to my
KPC3+. I mistakenly assumed that the disconnect side of it would be;
tnc-stop.kpc3 similar to its startup of tnc-startup.kpc3 but its not
that and now I can't stop the interface.

Bleah. That's bad --- xastir should complain when there is no file matching the name given, not hang like this. But there is no tnc-stop.kpc3, so that's
the issue.

In fact if I try to stop it Xastir freezes and won't quit, I have to
kill it. When I restart Xastir it still shows this interface as 'UP'
and nothing will make it stop. I also tried editing the properties to
change the it to tnc-stop.sys but it only causes Xastir to freeze up
again, any kind of edit here causes it to freeze.

I'm guessing there is someplace in a configuration file that I could
delete this interface from but I don't know where, can someone help me
here?

Yep. Just edit the file "~/.xastir/config/xastir.cnf" with your favorite
plain-text editor (vi/emacs/nano/pico or whatever) and remove the
reference to tnc-stop.kpc3. Should not be hard to find. It'll be on a line labeled "DEVICEn-TNC_DOWN-FILE" with "n" being the device number. You can replace it with "tnc-stop.sys" instead, which is a generic stop file that'll
work fine with the KPC3+.

--
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"Argue for your limitations and sure enough, they're yours." -- R. Bach



_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Reply via email to