[Dxspider-support] Cluster Locking up

[Dave Hawes]

On the subject of user_asc,

On 8 Oct 2007 at 12:05, Dirk Koopman wrote:

> Just a summary of what these things do:-
> 
> 1. create_sysop.pl : creates an *empty* user file just containing 
> entries for the node and the sysop callsign - *nothing* else.

What is the name of this "empty" file?  When I do create_sysop.pl, 
nothing at all shows up in spider\data.

I am doing a new installation on Windows 98, and Spider refuses to 
start because it can't find the spider\data\users file.  If I go to a 
previous version of Spider, which file do I bring over?

Also, the following sequence has no apparent effect:

cd spider\data
copy [from another directory] user_asc.o
perl user_asc.o

Nothing happens, other than a short pause and then back to the DOS 
prompt.  The attributes of user_asc.o are not changed, but nothing is 
created.

Any help appreciated.

73 - Dave N3RD

 
> 2. perl user_asc : recreates an entire user file from a backup. This 
> restores a corrupt user file (the normal reason why a node locks up or 
> SEGVs or gets other nasty errors). You don't need to do anything else 
> after one of these. Just restart the node.
> 
> 3. update_sysop.pl : changes the node and sysop records in the user file 
> to the things defined in the current DXVars.pm. An easy way of cloning a 
> node, is to copy a complete tree onto a new machine, do 2 above, edit 
> the local DXVars.pm with new details and then run update_sysop.pl. Don't 
> forget to change all the login details for your connect scripts on the 
> new machine to reflect the new node callsign (otherwise you will be 
> wondering how your connections keep disappearing)!