Updating option flags

[SpeedyVV]

Is there a way to update flags without shuting down and restarting a fold?

Specifically, sometimes I decide that I want to shut down a client for whatever reason, so what I do is add the -oneunit flag, shutdown folding and restarting.

This is the only way I know to do this.

Is there a way to update the flag (-oneunit specifically) or achieve the result I am looking for without terminating and restarting the folding client?

 

[APOLLO]

You might be able to do what you want with the tracker utility, but don't quote me on this without having tried it myself. I remember that flags can be turned on and off on the fly (I think).

 

[Tobit]

You might be able to do what you want with the tracker utility, but don't quote me on this without having tried it myself. I remember that flags can be turned on and off on the fly (I think).

Somewhat on the fly but the Tracker is just hiding what goes on in the background. The client is still stopped and restarted to make the changes.

Speedy, no.. what you are asking is not possible with the current clients. Hopefully this will be fixed with the new V7 client as it's been mentioned countless times.

 

[APOLLO]

Somewhat on the fly but the Tracker is just hiding what goes on in the background. The client is still stopped and restarted to make the changes..

I know how the tracker operates by shutting the client down and restarting it seamlessly if I got the gist of it correctly. BTW, how does PG feel about its function?

 

[Tobit]

BTW, how does PG feel about its function?

I don't think they care. The only time the Tracker was ever an issue for PG was in the very early days of development when the developers wanted to bundle the client with the Tracker. The current Tracker doesn't break the EULA in any way.

 

[SpeedyVV]

You might be able to do what you want with the tracker utility, but don't quote me on this without having tried it myself. I remember that flags can be turned on and off on the fly (I think).

Kool APOLLO. It does achieve the result I am looking for, Now, do I want to give up my trusty old HFM.NET? Uhmmm.

I'll take a look to see if they can co-live with each other. Tracker seems to support only local clients.

Thanks for the help.

EDIT: Just to clarify, I think I can use HFM.NET on my laptop to monitor all my boxen remotely. And use Tracker to manage the folding clients on my boxen.

 

[sirmonkey1985]

you dont have to give up hfm. i was using it with the tracker for the 3 hours i actually ran it. but i prefer running the 3 clients on their own then using the tracker. to much stuff going on and it it was easier just right clicking and closing the clients in the menu bar when i wanted to play games then clicking the 3 shortcuts to open them again.

 

[SazanEyes]

Actually, the tracker runs all WUs in -oneunit mode behind the scenes, so it doesn't need to shut down and restart when you change the configuration. When the WU finishes, the tracker will check its own config file to decide whether to start another WU or not.

The downside to this is that the fahlog file is recreated from scratch every time a new WU starts. If you use HFM.net, everything still works but your Complete/Failed WU count will always be 0. The tracker can't change that, but maybe HFM.net can add tracker support in the future (basically the ability to pull WU history from the optional archive files generated by the tracker).

 

[may i be worthy]

Actually, the tracker runs all WUs in -oneunit mode behind the scenes, so it doesn't need to shut down and restart when you change the configuration. When the WU finishes, the tracker will check its own config file to decide whether to start another WU or not.

The downside to this is that the fahlog file is recreated from scratch every time a new WU starts. If you use HFM.net, everything still works but your Complete/Failed WU count will always be 0. The tracker can't change that, but maybe HFM.net can add tracker support in the future (basically the ability to pull WU history from the optional archive files generated by the tracker).

You know, that is interesting, as I installed everything via the tracker, but now just run the FAH via shortcuts I made - but HFM does not see failed or complete units - I wonder what is different in the install..

 

[mekkanic]

The downside to this is that the fahlog file is recreated from scratch every time a new WU starts. If you use HFM.net, everything still works but your Complete/Failed WU count will always be 0. The tracker can't change that, but maybe HFM.net can add tracker support in the future (basically the ability to pull WU history from the optional archive files generated by the tracker).

So THATS why my completed units are always 0 when I use HFM.net.

Thanks for the info.

 

[dmaine]

i use both tracker and hfm , and found that i kept missing WU's on the work unit history until i figured out that under the preferences with the update at default, 5 min or so. The WU would complete, upload and start another before HFM would figure out that the WU was completed. Since i changed the update to 1 min, i only miss a WU occasionally and the history is more accurate.

 

[SazanEyes]

You know, that is interesting, as I installed everything via the tracker, but now just run the FAH via shortcuts I made - but HFM does not see failed or complete units - I wonder what is different in the install..

The F@H files are the same whether installed via the tracker or not (per PG license, the tracker can't modify the files). The tracker basically replaces the need to manually create shortcuts, and it passes the flags (including -oneunit) to the EXE when it runs the client. Since you created your own shortcuts, you are bypassing that process.

The F@H install is simple, but it's the multiple directories/shortcuts needed to run multi-GPU that are a pain, so that's why I like the tracker. Once I have a machine set up, though, I'd rather run F@H manually. Currently I just use the tracker on one of my SR-2s because I've been switching back and forth between multi-GPU and bigadv.