<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>Filter By Zone Issues/Troubleshooting with K1XX</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Charlie,</FONT>
</P>
<P><FONT SIZE=2>Thanks for the continued interest. My recollection is that the spots showed K1XX as the spotting station. It was this last weekend, during the CW contest. My node is only directly connected to one node, WR3D, but he is connected to a number of other nodes, including your system. It is my understanding that a spot originating from a station connected to your node would still show that station's callsign as the spotter, even after the spot had propagated to WR3D and on to my node. If you were not generating any spots this weekend then my understanding of how the system works is flawed, I am remembering these incidents incorrectly, or there is some other mystery afoot. I can interrogate the database and get some specifics on times for when the spots occurred, and you can check that at your end. As I said, your callsign was not the only one, just the one that stuck with me. If you let me know what type of info would be helpful, other than data on the spots, (and where to find it on the system if it is still available), I'll pass it along. Or, if it makes more sense and schedules could be worked out, maybe we could figure out a way to do some sort of a specific test or something...</FONT></P>
<P><FONT SIZE=2>Trivial side issue no. 2 - I noticed the times on some of the spots were off of actual UTC by a noticable amount (a min or so). My system is running chronyd to stay synched to UTC within a second or 2 via the internet. I woiuld think running chronyd or ntpd would be standard practice for nodes, no? </FONT></P>
<P><FONT SIZE=2>Anyway, thanks for the help. It would be fun to get this figured out, even if I decide to stay with the state filtering approach. Do you know the answer to the question about the need to update the usdb file periodically?</FONT></P>
<P><FONT SIZE=2>73 es tnx OM de KE0MF/Mike</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: charlie carroll [<A HREF="mailto:k1xx@ptcnh.net">mailto:k1xx@ptcnh.net</A>]</FONT>
<BR><FONT SIZE=2>Sent: Wednesday, February 19, 2003 6:24 PM</FONT>
<BR><FONT SIZE=2>To: The DXSpider Support list</FONT>
<BR><FONT SIZE=2>Subject: Re: [Dxspider-support] Filtering Issues - Updated</FONT>
</P>
<BR>
<P><FONT SIZE=2>Mike:</FONT>
<BR><FONT SIZE=2>Glad to hear that you got the by_state filter working. As far as</FONT>
<BR><FONT SIZE=2>by_zone, I'd still want to see more data, especially since you said some</FONT>
<BR><FONT SIZE=2>of the spots were coming from my node. Do you know who was issuing the</FONT>
<BR><FONT SIZE=2>spot? Frankly, I doubt that the zone overrides in cty.dat are the</FONT>
<BR><FONT SIZE=2>issue. There's a very small number of them.</FONT>
</P>
<P><FONT SIZE=2>73 charlie, k1xx</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Dxspider-support mailing list</FONT>
<BR><FONT SIZE=2>Dxspider-support@dxcluster.org</FONT>
<BR><FONT SIZE=2><A HREF="http://www.tobit.co.uk/mailman/listinfo/dxspider-support" TARGET="_blank">http://www.tobit.co.uk/mailman/listinfo/dxspider-support</A></FONT>
</P>
</BODY>
</HTML>