"Martin G. Diehl" wrote:

Alex Smariga wrote:

[snip]

The user_info.sah file did not have a good value im the 
"id=" line.  That caused SETIqueue to create a bogus queue 
for each instance of a corrupted user_info.sah. So far, 
3 PCs (out of 14) have been affected.  AFIK, no work units 
were being processed under the corrupted user_info.sah files.  

I copied a good version of the user_info.sah file to replace 
the corrupted one in the SETI directory of each of the 
affected PC's.  I also restarted each affected client PC's. 
SETIqueue served a new WU ... 

(should have added) ... After restarting SETIqueue, the extra 
queues were deleted automatically by SETIqueue.

and then [snip] deleted the bogus queues.

[snip]

-- 
Martin G. Diehl

Reality -- That which remains after you stop thinking 
about it.  

All replies and comments accepted and considered.  
Adoption of your suggestions are at my sole discretion.  
Award criteria are unpublished and are considered to 
be a trade secret.  As such, awards for your responses 
cannot be guaranteed.  Incoming flames may be stored 
for use during severe winters or may be circulated for 
deep analysis, peer review, and/or literary criticism.