I've noticed that it fails to send the work units and tries again after the next one. If your using Linux, you could kill it, and start it up again. Upon restart it will see that you have an unsent and finished work unit and try to send it again before starting on the current one.
-Rob > On 20020223.2333, Jim Beard said ... > > > I looked through the folding archives, and someone there said the time > limit was normally around 6 days. It took about 2 days for a work unit > on my machine. Did you folks do any config stuff or just fire up the > client and in name/team info? > On Saturday, February 23, 2002, at 09:18 PM, Mr O wrote: > > >Have you cranked out entire working units or just a few frames? I know > >there > >is a time limit to have WU's in by and somebody here knows what it is. > >I'm > >sure the info is also available on the website too. Other than that > >usually > >the site is updated every few hours. > > > >On Saturday 23 February 2002 09:04 pm, you wrote: > >>I got a question for you folding folks. I recently fired up the client > >>on my ole, idle pc and have cranked out a work unit or two now. But, > >>my > >>user info (JimB) isn't propagating in the folding.stanford web > >>pages. I > >>set my group to 668 but I haven't seen my WU show up in EugLug's info > >>yet. Does it take a while to get processed into the system or did they > >>just decide not to credit me for my cpu's work? > >> > >>Jim > > > >_________________________________________________________ > >Do You Yahoo!? > >Get your free @yahoo.com address at http://mail.yahoo.com > > > > > > > > -- Rob <rob_at_euglug_dot_net> my @euglugCode = qw(v+++ e--- eug+ bsd+++ gnu+ S+++);
