Task jumps to 70% immediately

[Peter_Hucker]

Why on earth would you want a different state after a reboot? A powercut doesn't change what processors you want folding to run on.

[aetch]

I always want FaH on my kit to default to paused if for some reason there is an unintended interruption (be it the client or wider os/hardware/power related) for a whole bag load of system management reasons.

I'm the same.
I do not want my systems to fold unless I explicitly tell them to.
I don't want folding to get in the way of maintenance activities or investigations I may be carrying out on the machine, especially something that requires multiple reboots.

I actually had a couple of power events earlier this week.
The first tripped all my systems, some systems just shut off, while others rebooted.
Not really anything to worry about, I think it was just a brownout.

The second event, which happened within 30mins, was a bit more troubling.
This had a slightly different outcome, it only tripped a couple of my systems.
That worried me, it forced me to consider that one of my machines had an issue and took out other systems at the same time.
After doing some testing I think it was just another brownout.

[Peter_Hucker]

I'm the same.
I do not want my systems to fold unless I explicitly tell them to.

But you did tell them to the last time you engaged folding. If you're going to restart a machine and you don't want it to fold upon doing so, you stop the folding first. I see no reason you'd want the state of FAH to be different before and after a reboot, especially if it's a power outage. What if you left computers folding while you're on holiday and some rebooted due to a powercut? You'd have them idling for no reason.

I actually had a couple of power events earlier this week.
The first tripped all my systems, some systems just shut off, while others rebooted.
Not really anything to worry about, I think it was just a brownout.

I set all mine to remember the last state in the BIOS, the same as I want FAH to do. If it's shut off at the wall due to a power outage, it should remember if it was on or off when the power comes back.

The second event, which happened within 30mins, was a bit more troubling.
This had a slightly different outcome, it only tripped a couple of my systems.
That worried me, it forced me to consider that one of my machines had an issue and took out other systems at the same time.
After doing some testing I think it was just another brownout.

Obviously some have a bigger bulk capacitor in the PSU, or you had a lower load on the PSU. Get a UPS and connect some big leisure batteries to it.

[Neil-B]

Why on earth would you want a different state after a reboot? A powercut doesn't change what processors you want folding to run on.

I manage a large amount of kit, personal and corporate - I have very good system management reasons for wanting to fully control my kit the way I want/need ... I don't intend to debate - your experiences/mindset/knowledge is different to mine ... Fact - some folders do not agree with you ... Fact- the FaH system does what it does and for the time being that is unlikely to change ... Please have the courtesy to understand that some other people may know what they are doing and chose to act differently to the way you do.

[Peter_Hucker]

You would be fully in control, that's the point you're missing. When you tell your computer to fold, or to not fold, that instruction should remain until you say otherwise. But at the moment you're not in control. A powercut could cause it to stop or start folding when you don't want it to. This is not an opinion, it's basic common sense, something considerably lacking in today's society.

[Neil-B]

So now you are feeling feel to insult others based on your opinions ... rofl ... I suggest to you that I know exactly what will happen to my kit under various scenarios and tbh it is set to react exactly the way I wish it to - it is being managed and controlled precisely how I see fit ... your assumptions about other peoples levels of knowledge/sense are uncalled for and erroneous

[Joe_H]

I have locked this topic and moved posts to be no longer visible as it degenerated into name calling.

To the OP, the client does what it does, and does it for valid reasons from experience and user suggestions in the past. No further work is planned on the version 7 client. There is an API and command interface that can be used to have the client act in almost any specific manner you want. You are welcome to make suggestions on the new version once they start release of that.