(I don't think SetiQ will let you transfer wu's to a queue for a different client) I recommend using a public SetiQ server, even if your using SetiQ yourself. You get double-buffered against these S@H outtages since the public server will cache wu's for you, and your SetiQ is caching wu's for your machines also.
Anyone know what is causing the problem with S@H? I did see a notice on their web page about a 1 hr outtage on Monday the 18th. >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On >Behalf Of Jeff Gerst >Sent: Sunday, March 17, 2002 10:16 AM >To: [EMAIL PROTECTED] >Subject: Re: SetiQueue Problems > > > >login to your SetiQueue and click on tools there u will find what >you need, but >you do have to be logged in on the web interface... > >Bruce Hudgens wrote: > >> Seti has been down since yesterday. I am running SetiQueue that >has 42 WUs >> queued in the 3.06 queue but none in the 3.07 queue. I have been in the >> process of updating my computers to the v3.07 client. At this >point, seven >> computers are running v3.07 and two computers are running v3.06, >thus only >> two computers are doing any work. Does anyone know how to transfer WU >> between queues? Any help in getting my system running again will be >> greatly appreciated. == Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html This list sponsored by talkspace.net: building space communities online. Mailing list services provided by klx.communications -- www.klx.com
