On Mon, 22 Sep 2008, Curt, WE7U wrote:
The "p = NULL;" at x_spider.c line 544 is the culprit. Comment that
line out and the server ports seem to be as solid as they ever were.
Fixed in CVS of course.
--
Curt, WE7U. archer at eskimo dot com
http://www.eskimo.com/~a
1.9.2 OK (w/error output when client disconnects)
1.9.3-2008-Jun-09 OK (w/error output when client disconnects)
1.9.3-2008-Jul-07 Problem
1.9.4 Problem
1.9.5 Problem
I see this on the xterm I started the server from
w/"1.9.3-2008-Jun-09", but it continues
On Sun, 21 Sep 2008, Josh Housey wrote:
Its been running fine from 190 and even with this version, but I
cannot reconnect it by getting "connected refused".
For example, I just did a regular telnet connection to it through
the console (works the same through the other Xastir). and it
states tha
To: xastir@xastir.org
Subject: [Xastir] Problem with Xastir Server Ports
Dear All,
I have been running Xastir on a Linux laptop running Slackware 11.0 for my
packet "server" and also run it on a Mac Mini as well.
I use the Mac mini's Xastir to view the traffic and get on to APRS via
lapto
Dear All,
I have been running Xastir on a Linux laptop running Slackware 11.0 for my
packet "server" and also run it on a Mac Mini as well.
I use the Mac mini's Xastir to view the traffic and get on to APRS via laptop
through Xastir's Server Ports.
Its been running fine from 190 and even with
