[Dxspider-support] Check_build
Dirk Koopman
djk at tobit.co.uk
Fri Mar 24 15:06:51 GMT 2023
It is not necessary to do a 'load/cmd' unless you happen to be me and
doing something weird with file modification times. The DXCommand system
automatically a) picks up new commands when you use them and b) will
automatically update the command if the file modification time is newer
than the one currently stored in the node. All 'load/cmd' does is clear
the command cache and therefore *any* command used will (now) be 'new'.
It makes writing DXSpider commands sooo... much easier. This is a
fundamental part of DXSpider and was there since the first ever issued
version of the program (I like to think ahead). It means that one can
write new commands and try them out on running test nodes. Have a
watchdbg running and try the command in a console.pl, if it fails it
will output in both the console and (in a more detailed fashion) in
watchdbg. Rinse and repeat until working. No node restarts required.
Enjoy.
Dirk G1TLH
On 24/03/2023 14:30, Kirill Ryabov via Dxspider-support wrote:
> Bjorn
> You need to place check_build.pl to /spider/local_cmd then in DXSpider
> console type 'load/cmd' to load this command. After that you can run
> this command under DXSpider console, just type 'check_build Y' if you
> want to make a backup of the current DXSpider build. If yopu don't
> want to make a backup just run 'check_build'.
>
> The crontab is located also in /spider/local_cmd
>
> 73
> Kirill
> R5ACQ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230324/4fbb4de6/attachment.htm>
More information about the Dxspider-support
mailing list