Feature Name:
option to retain old fahlog.txt
What does this feature do:
prevents fahtracker from deleting the fahlog aftr a completed wu
Why would this feature be useful to be include in the tracker:
specifically for me, I run 3 rigs for folding, but since they are all in my basement to keep heat and noise away from my upstairs I monitor all the clients from my laptop which does not fold using HFM.. I would like to see if any clients have failed for any reason, but since the fahlog gets wiped I have to go downstairs and look on each individual rig's fahtracker records to check them. If the fahlog stayed the way it does when running a normal client without the tracker, you can see the number of completed/failed wu's from one central monitoring point (hfm, or a separate monitor only console you havent started writing yet *hint)
I think this would be an option others would appriciate also. I am unaware of why fahtracker deletes the log each time also.. anyone able to explain that one?
Thanks
- Jay
option to retain old fahlog.txt
What does this feature do:
prevents fahtracker from deleting the fahlog aftr a completed wu
Why would this feature be useful to be include in the tracker:
specifically for me, I run 3 rigs for folding, but since they are all in my basement to keep heat and noise away from my upstairs I monitor all the clients from my laptop which does not fold using HFM.. I would like to see if any clients have failed for any reason, but since the fahlog gets wiped I have to go downstairs and look on each individual rig's fahtracker records to check them. If the fahlog stayed the way it does when running a normal client without the tracker, you can see the number of completed/failed wu's from one central monitoring point (hfm, or a separate monitor only console you havent started writing yet *hint)
I think this would be an option others would appriciate also. I am unaware of why fahtracker deletes the log each time also.. anyone able to explain that one?
Thanks
- Jay