Here's my .conf:
{
"pools" : [
{
"url" : "stratum.btcguild.com:3333",
"user" : "username",
"pass" : "x"
}
],
"failover-only" : true,
"klondike-options" : "350,55"
}
350 refers to the MHz and 55 to the max temp before it pauses to cool down. I plan on changing my max temp to 65 this weekend, but to get it into the 60s you need to compile cgminer yourself after editing it.
I was under the impression that the temp setting under klondike-options was a target temperature. ie...If you have the PWM fan hooked up it will increase fan speed any time the temp crosses above 55 and decrease speed when below 55. I would think setting your target temp higher than the killwork value would result in a lot of thermal throttling. If you have your fan hooked straight to the 12v molex connector I don't think the target temp setting would ever come in to play since the fans would be running wide open 100% of the time.
As you said above, cgminer is hard coded to kill work on the klondike at 53.5C and resume when temps fall to 45.5C. I have been unable to get my K16's to hash above 352mhz. It's winter here, but I have yet to see my K16's go above 53C with my target temp set to 50C and driver-klondike.c modified to kill work at 65.5C. At night when it gets colder my K16's have been running around 45-47C at 352mhz.
Chad