[Dxspider-support] export_user command

[Tom Vavra]

The users_asc files are stand-alone programs that will rebuild your users.v3 file should it get trashed.    ./users_asc    from /spider/data   will delete the old file and rebuild it as it was at the time of the export-user.  Spider must not be running to rebuild.

A comment about users.v3 growing so large.  Every time a PC41 is received by your node it enters the data in users.v3.  If there is not an entry for that particular callsign, one is created.  The entries are not limited to your registered users and the nodes you see.

      Tom   WB8ZRL
  ----- Original Message ----- 
  From: Bill Coleman N2BC 
  To: The DXSpider Support list 
  Sent: Thursday, October 28, 2004 2:33 PM
  Subject: [Dxspider-support] export_user command


  My DXSpider cluster has been quite well behaved for eons.  Most recent changes are a switch to K1EA for spot feeds and updated WINXP to SP2.   Over the past couple weeks the 10G harddrive has filled twice.

  The users_asc file was 7Gb in both cases.

  Now I see that the base CRONTAB file has an export-user command in it.  I have commented it out.  I have also deleted the 5 generations of users_asc (the .o, .oo, .ooo  etc.).

  Another observation, my users.V3 is 8Mb - I thought (dangerous) that this would only have my registered users, but it obviously has many many more.

  So, finally, to my questions:

  1) Is there something abberant about my users.V3 file?
  2) What is the purpose of the export_user command in the base CRONTAB file?  I cannot find a companion import function for rebuild or ???

  Thanks for reading this novel :-)

  Best 73, Bill  N2BC



------------------------------------------------------------------------------


  _______________________________________________
  Dxspider-support mailing list
  Dxspider-support at dxcluster.org
  http://www.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tobit.co.uk/pipermail/dxspider-support/attachments/20041029/c4a081e5/attachment.html