This is typical of the last few days.
The client will try and get a new unit, and if it fails, wait for an hour before trying again. If that fails, then it shuts down with the message you've got. I can only suggest that you either get SetiDriver (to build a cache of WU's) so you can keep crunching, and then uplink during the Californian night-time, when the servers are more accessible. Hope this helps. Patrick, Proud Member of Team Picard! ----- Original Message ----- From: "Dan Crooks" <[EMAIL PROTECTED]> To: "Setiathome" <[EMAIL PROTECTED]> Sent: Tuesday, January 29, 2002 11:16 PM Subject: Weird Report > > I found this in my nohup.out file today after finding my client not running. > Has anyone else had this happen? I am wondering if there is a problem in > the > client code. Or is this possibly related to their bandwidth restrictions? > > > > Done with work unit. > Sending result - connecting to server. > All data sent. > SETI@home account summary: > Name: > Data units completed: 5113 > Total computer time: 71067 hr 19 min 40.5 sec > Found data file: no. Found result header file: no. > Getting data - connecting to server. > Can't open file stop_after_send.txt == 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
