It is really pretty simple to move wu's around.
Make sure both clients are stopped!!!!!!
I have an empty 'temp wu' folder in each of my folding folders (ie folder=directory).
Cut (ie move) the WORK directory, queue.dat from one of the instances folding directories to its temp wu directory. Make sure the temp wu dir is empty first !!!! ... it should be if you always cut and paste into and out of it ... but sometimes i do forget, or use copy not cut if i want to save it just in case i screw up
You can use the 'undo' when you make a mistake as long as you do it right away. Also, if the temp wu directory already has a wu in it ... wxp will prompt you to replace it ... you should CANCEL and figure out why you have a wu in there already before proceeding!
Then cut and paste (ie. move) the work dir and queue.dat from the other STOPPED 2'nd instance into the first instance's dir (Not into the temp wu directory since it is already holding a wu).
Finally, cut and paste (move) the work dir and queue.dat from the temp wu dir in the first instance to the second instance's dir.
Restart the clients and they will pick up where they left off.
I have file shares setup between all my folding rigs ... i always put my folding instances on D: in directories called FAH#1 and FAH#2.
When I do the move have 1 instance of windoze explorer open for each of the source and target instances. Helps avoid confusion.
Since my 16 farm rigs (ie 32 instances) are all on kvms, sometimes i can't see the screens for both rigs at the same time if they are on the same kvm. So you can check you are moving a stopped wu by looking at the bottom of fahlog.txt for that instance and the last message should be a client shutdown message ... 'terminated by sigterm' on my consoles.
Sometimes when i am in a rush, and cut a running wu by mistake ... windoze explorer will tell you it can't move a file thats in use. If you immiediately undo the move (under 'file' pull down menu) everything will be ok 99.9% of the time and you will not have a corrupted wu. This won't happen if you select the right wu
I also include the unitinfo.txt when i move wu's ... its not necessary but it gives me a way to easily see which wu i am looking at. Especially helpful if i get interrupted or am moving 3 wu's around at once --- it is easy to get confused. Unitinfo.txt is only ever written by the clients ... you can delete it anytime and it will get rewritten by the client on its next frame update.
Make sure both clients are stopped!!!!!!
I have an empty 'temp wu' folder in each of my folding folders (ie folder=directory).
Cut (ie move) the WORK directory, queue.dat from one of the instances folding directories to its temp wu directory. Make sure the temp wu dir is empty first !!!! ... it should be if you always cut and paste into and out of it ... but sometimes i do forget, or use copy not cut if i want to save it just in case i screw up
You can use the 'undo' when you make a mistake as long as you do it right away. Also, if the temp wu directory already has a wu in it ... wxp will prompt you to replace it ... you should CANCEL and figure out why you have a wu in there already before proceeding!Then cut and paste (ie. move) the work dir and queue.dat from the other STOPPED 2'nd instance into the first instance's dir (Not into the temp wu directory since it is already holding a wu).
Finally, cut and paste (move) the work dir and queue.dat from the temp wu dir in the first instance to the second instance's dir.
Restart the clients and they will pick up where they left off.
I have file shares setup between all my folding rigs ... i always put my folding instances on D: in directories called FAH#1 and FAH#2.
When I do the move have 1 instance of windoze explorer open for each of the source and target instances. Helps avoid confusion.
Since my 16 farm rigs (ie 32 instances) are all on kvms, sometimes i can't see the screens for both rigs at the same time if they are on the same kvm. So you can check you are moving a stopped wu by looking at the bottom of fahlog.txt for that instance and the last message should be a client shutdown message ... 'terminated by sigterm' on my consoles.
Sometimes when i am in a rush, and cut a running wu by mistake ... windoze explorer will tell you it can't move a file thats in use. If you immiediately undo the move (under 'file' pull down menu) everything will be ok 99.9% of the time and you will not have a corrupted wu. This won't happen if you select the right wu
I also include the unitinfo.txt when i move wu's ... its not necessary but it gives me a way to easily see which wu i am looking at. Especially helpful if i get interrupted or am moving 3 wu's around at once --- it is easy to get confused. Unitinfo.txt is only ever written by the clients ... you can delete it anytime and it will get rewritten by the client on its next frame update.
Last edited:
