Quote:
Originally Posted by KarmaKiller  FRIDAY!!! 
Core still going good, now it just doesn't want to send results.. 
I'll mess with it when I get home..
Morning Dave! TGIF to ya! |
KK,
I've read on the F@H forum that sending results manually is really unnecessary especially if you are connected 24x7. The client will send completed results every so often. As a matter of fact if you are using the console add -verbosity 9 to you shortcut. It should write all the stuff that is happening on the client to the log file and you console screen. Every so often the client will try to send any unsent wu again.
[07:15:31] Completed 1475000 out of 2500000 steps (59 percent)
[07:30:31] Timered checkpoint triggered.
[07:45:31] Timered checkpoint triggered.
[08:00:31] Timered checkpoint triggered.
[08:15:31] Timered checkpoint triggered.
[08:27:03] - Autosending finished units...
[08:27:03] Trying to send all finished work units
[08:27:03] + No unsent completed units remaining.
[08:27:03] - Autosend completed
[08:30:32] Timered checkpoint triggered.
[08:45:33] Timered checkpoint triggered.
[09:00:32] Timered checkpoint triggered.
[09:15:33] Timered checkpoint triggered.
[09:30:34] Timered checkpoint triggered.
[09:32:08] Writing local files
[09:32:08] Completed 1500000 out of 2500000 steps (60 percent)
This is what it looks like when I start the console. For those that are running it as a service there is also a way by adding it to the service console on the os.
Launch directory: D:\FAHSMP
Executable: D:\FAHSMP\fah.exe
Arguments: -verbosity 9
[14:27:02] - Ask before connecting: No
[14:27:02] - User name: engracio (Team 111)
[14:27:02] - User ID: 662DD26B3654730F
[14:27:02] - Machine ID: 4
Of course if the wu is expiring soon and you need to send it in asap, then you must do it manually. Btw this box is my dual 2.8 xeon. Its sister died about 3 months ago It is showing her age when I switch back in forth between the xeon and the quaddie.
I plan to keep her since I got her setup with a raid 1 and keep all of my data.