How do I..?

[Tithulta]

Check to see if anything is not being sent in from the queue? i've seen a post and tried to do what it said , but the F@H doesn't do what they said it'd do...it barely flashes on the screen long enough to know it even tried. Can someone tell me how to check queue status? please be extremely plain and descriptive so I can get it right. I;ve done a few villins and now i'm working on another and it's my wudata#6..so i'm wondering if I ahve 5 sitting in queue not being sent.

[Dunga Bee]

I usually will just open up the FAHlog.txt file, go to the bottom and then scroll up until you see the text where it is trying to connect to the server.

If you see a bunch of "trying to send / could not send results" then you have some still in the queue. Success should look like this:


Folding@Home2 Core Shutdown: FINISHED_UNIT
CoreStatus = 64 (100)
Sending work to server

+ Attempting to send results
- Reading file work/wuresults_08.dat from core
(Read 469761 bytes from disk)
- Connecting to server (171.64.122.111)
+ Connection established
+ Results successfully sent
+ Finished WU 8
Working on Unit 08


I am on WU 9 and my last send was good, so I do not think that having a WU number above 1 means that there is a ton of stuff in your queue to send.

And, even if you have some failed results, they will eventually send. Your stats may just drop temporarily since your results are not being posted, but then they'll jump back up when you dump all those results at once. Any queued results are attempted every time you complete a protein.

Hope that helps. If not, let me know what I can do.

DB

[Kendan]

Are you using the graphical ver. or the text ver.?
here is the link to you on F@H2: http://folding.stanford.edu/cgi-bin/userpage?q=Tithulta
remember what is there and go back after the next couple of updates and see if it matches up.
Fold on!!!

[Tithulta]

I'm using the text version on both my systems...there doesn't appear to be anything in the queue so I guess I'm ok. I suppose it goes thru 9 before starting back at 1. Thanks hadn't thought of checking the FAHlog file.