- Joined
- Nov 29, 2004
- Location
- T3h Intr@tub3z!
If you use the Service/Console setup of F@H, then this is an example of what it should "GENERALLY" look like and explanations for each part. I will use double stars ** to denote a description of each line... I am taking this info from my client.cfg, so realize this doesn't cover every concievable option, but i believe is pretty darn close. The [http] section is left incomplete, as I haven't been able to find definitions for any of those entries.
ALSO, A BIG THANKS TO CHASR FROM OCFORUMS.COM FOR HELPING ME FIX A FEW MISTAKES IN MY DEFINITIONS.
[settings]
username=F(OC)LD
**obvious, the name that shows up when you turn in work**
team=32
**the team you fold for, in this case, Team32 is Overclockers.com**
asknet=no
**should the machine ask for permission before uploading complete work? Really only useful in a dial-up situation, or if you have certain times of the day you are allowed net access**
machineid=1
**this is very useful when folding more than one instance on a PC, example: DualProc or DualCore systems, or Hyperthreaded systems. Machineid can be 1-8, which means you can have up to 8 instances at once on a single machine, provided you have the CPU's and RAM to do it.**
local=548
**this shows how many WU's this machine (or instance if more than one instance on a machine) has completed to date. It's a good way to keep track on how much work (not how many points, but how many WU's) that one instance of F@H has done. This also shows up in the FAHLog.txt when you have the (without quotes)"-verbosity 9" flag turned on. In this case, my machine has done 548 wu's since this instance of F@H was installed (had quite a few EUE's while attempting to OC this thing and get it folding stable, but it never happened to be stable to fold at ANY OC)**
bigpackets=yes
**allows downloading of WU's greater than 5mb in size. These usually have bonus points and are worth the most, but can take up huge chunks of RAM, especially the QMD's.**
[http]
active=no
host=localhost
port=8080
usereg=no
[clienttype]
type=1
**1 = Normal. 2 = Machine is too slow to finish normal WU's, so if you give it a 2 as client-type, it will only ask for and fold Timeless WU's. If you are running console version 5.04, then a type=3 is the same as putting in the -advmethods flag**
nonet=yes
**when combined with type=2, this will cause the client to download 10 deadlineless WUs. The client will regularly (6 hours) attempt to connect to the net after the completion of 7 to upload completed WUs and download 7 new ones.**
[core]
priority=0
**0=idle priority, it folds when nothing else is using the CPU. 1=Low Priority. I do not recommended priority=1 unless it is a dedicated folding boxen that is used for NOTHING else but folding.**
cpuusage=100
**how much of the CPU's power it will use when folding. This WILL scale back as the user demands more and more of the CPU**
disableassembly=no
**Setting this to yes would disable assembly optimizations (SSE, SSE2, 3DNow) and slow all WUs using cores other than Tinker and Amber to a crawl. Only disable optimizations on a machine that is unstable when using SIMD optimizations.**
checkpoint=30
**frequency of intermediate checkpoints. A checkpoint is written at the completion of every frame plus intermediately at checkpoint=xx (30 being max). It doesn't hurt production much on most WU's, but it doesn't make much sense to have the checkpoint set to anything other than 30 on rigs running 24/7 unless power failures or system hangs occur frequently. It makes no sense if you're folding QMDs to set checkpoints to 15 if it takes 15'10" to complete a frame. The two checkpoints will be 10 seconds apart then 15 minutes. Tinkers don't use intermediate checkpoints.**
ignoredeadlines=no
**set this to yes if you're in the process of overclocking your machine. Set to no, if the clock resets to bios day one, ususlly several years in the past, you'll lose every WU you submit that was downloaded with the wrong date.**
[power]
battery=no
**useful only for laptops. When it detects that the lappy is running in battery-mode only, then F@H will shut down if this option is turned to yes**
and here is my client.cfg to see what it looks like WITHOUT the definitons. Remember, this is for my machine and these settings may not work for everyone.
ALSO, A BIG THANKS TO CHASR FROM OCFORUMS.COM FOR HELPING ME FIX A FEW MISTAKES IN MY DEFINITIONS.
[settings]
username=F(OC)LD
**obvious, the name that shows up when you turn in work**
team=32
**the team you fold for, in this case, Team32 is Overclockers.com**
asknet=no
**should the machine ask for permission before uploading complete work? Really only useful in a dial-up situation, or if you have certain times of the day you are allowed net access**
machineid=1
**this is very useful when folding more than one instance on a PC, example: DualProc or DualCore systems, or Hyperthreaded systems. Machineid can be 1-8, which means you can have up to 8 instances at once on a single machine, provided you have the CPU's and RAM to do it.**
local=548
**this shows how many WU's this machine (or instance if more than one instance on a machine) has completed to date. It's a good way to keep track on how much work (not how many points, but how many WU's) that one instance of F@H has done. This also shows up in the FAHLog.txt when you have the (without quotes)"-verbosity 9" flag turned on. In this case, my machine has done 548 wu's since this instance of F@H was installed (had quite a few EUE's while attempting to OC this thing and get it folding stable, but it never happened to be stable to fold at ANY OC)**
bigpackets=yes
**allows downloading of WU's greater than 5mb in size. These usually have bonus points and are worth the most, but can take up huge chunks of RAM, especially the QMD's.**
[http]
active=no
host=localhost
port=8080
usereg=no
[clienttype]
type=1
**1 = Normal. 2 = Machine is too slow to finish normal WU's, so if you give it a 2 as client-type, it will only ask for and fold Timeless WU's. If you are running console version 5.04, then a type=3 is the same as putting in the -advmethods flag**
nonet=yes
**when combined with type=2, this will cause the client to download 10 deadlineless WUs. The client will regularly (6 hours) attempt to connect to the net after the completion of 7 to upload completed WUs and download 7 new ones.**
[core]
priority=0
**0=idle priority, it folds when nothing else is using the CPU. 1=Low Priority. I do not recommended priority=1 unless it is a dedicated folding boxen that is used for NOTHING else but folding.**
cpuusage=100
**how much of the CPU's power it will use when folding. This WILL scale back as the user demands more and more of the CPU**
disableassembly=no
**Setting this to yes would disable assembly optimizations (SSE, SSE2, 3DNow) and slow all WUs using cores other than Tinker and Amber to a crawl. Only disable optimizations on a machine that is unstable when using SIMD optimizations.**
checkpoint=30
**frequency of intermediate checkpoints. A checkpoint is written at the completion of every frame plus intermediately at checkpoint=xx (30 being max). It doesn't hurt production much on most WU's, but it doesn't make much sense to have the checkpoint set to anything other than 30 on rigs running 24/7 unless power failures or system hangs occur frequently. It makes no sense if you're folding QMDs to set checkpoints to 15 if it takes 15'10" to complete a frame. The two checkpoints will be 10 seconds apart then 15 minutes. Tinkers don't use intermediate checkpoints.**
ignoredeadlines=no
**set this to yes if you're in the process of overclocking your machine. Set to no, if the clock resets to bios day one, ususlly several years in the past, you'll lose every WU you submit that was downloaded with the wrong date.**
[power]
battery=no
**useful only for laptops. When it detects that the lappy is running in battery-mode only, then F@H will shut down if this option is turned to yes**
and here is my client.cfg to see what it looks like WITHOUT the definitons. Remember, this is for my machine and these settings may not work for everyone.
Code:
[settings]
username=F(OC)LD
team=32
asknet=no
machineid=1
local=548
bigpackets=yes
[http]
active=no
host=localhost
port=8080
usereg=no
[clienttype]
type=1
[core]
priority=0
cpuusage=100
disableassembly=no
checkpoint=30
ignoredeadlines=no
[power]
battery=no
Last edited: