[Dxspider-support] HamClock 3.03

[Dirk Koopman]

You might like to point out to the author that DXSpider will send a 
command prompt every 11 minutes (default) if no activity has occurred on 
a connection. This occurs irrespective of what/who else is connected to 
a node or what might be passing through. If an individual connection has 
neither received nor sent data in the last $main::user_interval (set to 
11*60 seconds on node startup) then it *will* be sent a prompt. Each 
connection has its own individual timer.

This is a genuine "original feature" of the code (circa 1997/8) and was 
chosen specifically to keep a BPQ node circuit open.

On a modern system this will likely only happen if a node has lost all 
its neighbour node connections or the user has screwed (whether 
deliberately or not) his filters down too far.

73 Dirk G1TLH

On 20/01/2024 22:49, Keith Maton via Dxspider-support wrote:
> Released today.
>
> From the release notes:
>
>   * fix: DX Cluster locations no longer use show/heading command
>
>
> It’ll take a while for people to start switching to this version and 
> once they do, HamClock will be quiet as a mouse on the node.  When it 
> connects, it sends a set/qra and set/location and apart from 
> keep-alive pings every ten minute pings during periods of inactivity, 
> that’s it.  It doesn’t send any other commands.
>
> I really hope that this is a satisfactory conclusion to the matter and 
> this can be put to bed now.
>
> 73 Keith G6NHU
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240121/4925c857/attachment.htm>