<div dir="ltr">Gotcha.  Makes sense.<div><br></div><div>One more quick question... does the "reset" knock all the connections off the node, but leave the node's "uptime" continuous?</div><div><br></div><div>Mike, WA9PIE</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 12, 2016 at 1:39 PM, Dirk Koopman <span dir="ltr"><<a href="mailto:djk@tobit.co.uk" target="_blank">djk@tobit.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>It depends on how old the git
      repository is when you do the update. If you update at or near a
      change to the repository then, generally, it will have the latest
      version of cty.dat. On the other hand if you update cty
      religiously, but git pull only occasionally, then there will be a
      reset to a previous version. But then, if you are updating cty
      religiously, that will right itself fairly soon.<br>
      <br>
      Bear in mind that I use cty data for country and maybe state
      information for those stations on the cluster that haven't set
      their lat/long. This is used for things like beam heading etc, not
      QSL, contesting or other more detailed uses - so I don't believe
      that an absolutely up to date cty is going to be critical. Also,
      while cty has some specific info on individual callsigns of
      interest, these are pruned regularly and so it may be that the
      historical record contained in the spots can't be matched up with
      the current cty data. Indeed there are countries and/or in my spot
      records going back  to 1997 that don't exist any more.<span class="HOEnZb"><font color="#888888"><br>
      <br>
      Dirk</font></span><div><div class="h5"><br>
      <br>
      On 12/08/16 19:14, Michael Carper, Ph.D. wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">
      <div dir="ltr">Thanks, Dirk.  Then let me ask you the next logical
        question...
        <div><br>
        </div>
        <div>Is it ever possible then that the version of CTY that's in
          the latest build could back-rev a newer version that's already
          installed?</div>
        <div><br>
        </div>
        <div>Mike, WA9PIE</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Fri, Aug 12, 2016 at 1:09 PM, Dirk
          Koopman <span dir="ltr"><<a href="mailto:djk@tobit.co.uk" target="_blank">djk@tobit.co.uk</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <div>Yes. <br>
                <br>
                Dirk
                <div>
                  <div><br>
                    <br>
                    On 12/08/16 15:50, Michael Carper, Ph.D. wrote:<br>
                  </div>
                </div>
              </div>
              <blockquote type="cite">
                <div>
                  <div>
                    <div dir="ltr"><span style="font-size:12.8px">When
                        you run these commands:</span>
                      <div style="font-size:12.8px"><br>
                      </div>
                      <div style="font-size:12.8px">
                        <div>git reset --hard<br>
                        </div>
                        <div>git pull</div>
                      </div>
                      <div style="font-size:12.8px"><br>
                      </div>
                      <div style="font-size:12.8px">Does the resulting
                        update overwrite the pre-existing CTY files?</div>
                      <div style="font-size:12.8px"><br>
                      </div>
                      <div style="font-size:12.8px">Mike, WA9PIE</div>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                  </div>
                </div>
                <pre>______________________________<wbr>_________________
Dxspider-support mailing list
<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mai<wbr>lman/listinfo/dxspider-support</a>
</pre>
    </blockquote>
    

  </div>


______________________________<wbr>_________________

Dxspider-support mailing list

<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a>

<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">http://mailman.tobit.co.uk/mai<wbr>lman/listinfo/dxspider-support</a>


</blockquote></div>
</div>


<fieldset></fieldset>
<pre>______________________________<wbr>_________________
Dxspider-support mailing list
<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/<wbr>mailman/listinfo/dxspider-<wbr>support</a>
</pre>

</blockquote>
</div></div></div><br>______________________________<wbr>_________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a><br>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">http://mailman.tobit.co.uk/<wbr>mailman/listinfo/dxspider-<wbr>support</a><br>
<br></blockquote></div><br></div>