[Dxspider-support] Does updating DXSpider over-write pre-existing CTY files?

[Michael Carper, Ph.D.]

Thanks, Dirk.

On Fri, Aug 12, 2016 at 3:17 PM, Dirk Koopman <djk at tobit.co.uk> wrote:

> No, it just affects the source. All the main source been compiled into
> memory by then. It won't take effect until you next restart the node.
>
> Needless to say it isn't *quite* as simple as that because commands are
> reloaded in real time as they are used.
>
> Dirk
>
>
> On 12/08/16 20:56, Michael Carper, Ph.D. wrote:
>
> Gotcha.  Makes sense.
>
> One more quick question... does the "reset" knock all the connections off
> the node, but leave the node's "uptime" continuous?
>
> Mike, WA9PIE
>
> On Fri, Aug 12, 2016 at 1:39 PM, Dirk Koopman <djk at tobit.co.uk> wrote:
>
>> 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.
>>
>> 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.
>>
>> Dirk
>>
>>
>> On 12/08/16 19:14, Michael Carper, Ph.D. wrote:
>>
>> Thanks, Dirk.  Then let me ask you the next logical question...
>>
>> 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?
>>
>> Mike, WA9PIE
>>
>> On Fri, Aug 12, 2016 at 1:09 PM, Dirk Koopman <djk at tobit.co.uk> wrote:
>>
>>> Yes.
>>>
>>> Dirk
>>>
>>>
>>> On 12/08/16 15:50, Michael Carper, Ph.D. wrote:
>>>
>>> When you run these commands:
>>>
>>> git reset --hard
>>> git pull
>>>
>>> Does the resulting update overwrite the pre-existing CTY files?
>>>
>>> Mike, WA9PIE
>>>
>>>
>>> _______________________________________________
>>> Dxspider-support mailing listDxspider-support at dxcluster.orghttp://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>> _______________________________________________ Dxspider-support
>>> mailing list Dxspider-support at dxcluster.org
>>> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> _______________________________________________
>> Dxspider-support mailing listDxspider-support at dxcluster.orghttp://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> _______________________________________________ Dxspider-support mailing
>> list Dxspider-support at dxcluster.org http://mailman.tobit.co.uk/mai
>> lman/listinfo/dxspider-support
>
> _______________________________________________
> Dxspider-support mailing listDxspider-support at dxcluster.orghttp://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20160812/257512e6/attachment-0001.html>