<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">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'. <br>
<br>
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 <strike>running</strike>
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. <br>
<br>
Enjoy.<br>
<br>
Dirk G1TLH<br>
<br>
On 24/03/2023 14:30, Kirill Ryabov via Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:cfe99db1-11a3-b39f-2958-d3c61d2fd28a@mail.ru">Bjorn
<br>
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'.
<br>
<br>
The crontab is located also in /spider/local_cmd
<br>
<br>
73
<br>
Kirill
<br>
R5ACQ
<br>
</blockquote>
</body>
</html>