Mini-HowTo: HowTo look at your current log forever WHILE Folding.
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
I have crashed my client and core with no error shown by doing this:
While client runs, look at client's CURRENT log for enough time that the client wants to write to it. When it cannot and times out after a period of not being able to, it WILL abend suddenly. Linux does not do file lookats this way, and I will explain how because how to do it in Windows will become suddenly quite apparent also (Some of us do fold in Linux, too.).
Linux has this command, called cat and it is short for catalog. ALL this command does is to make a copy of the file it is told to catalog and throw the copy up on the screen but it does so so fast that you cannot read it until the last part is sitting on the screen-- then you just see the end, but I often like to scroll up and down through all of a log for various reasons. Linux has another command, and the cat result can be piped to it. It's called less. Command becomes cat FAHlog.txt | less and les lets you use Page Up and Page Down and Home (top of file, first lines) and Edn and arrow keys to go back and forth as long as you want in a copy of a file sitting in RAM that is made by cat when you do this pipe ( | ) from cat to less.
IMPORTANT POINT which you can make use of in Windows also--cat makes a copy, and you can in Windows also. Then you can read the copy all day, the folding client can write to original, and the folding client will not suddenly choke. So far as I can find out by looking and testing, this behavior is replicable across the Linux and Windows clients through Client Version 5.02. Fixing the client to not choke could be a real PITA of a thing to do. Avoiding this weird issue is not at all bad nor hard to do.
Word and Wordpad can read copies they generate of files that another program (aka application) is using the original one of. So can WordPerfect and Open Office. Notepad normally does not check to see if the file is in use, it just grabs it. Wordpad OFFERS to make a copy if the file appears to be in use, and it can read text files. So, open your current log in one of the programs listed above OTHER tHAN Notepad) and it is likely that if the folding client is on that they will offer to make a copy of the file and let you look at that instead of the original. Let them do this, and the client can write to original while you read a copy made as a snapshot of file at the time you opened your program to read the file. OR, tell Windows Explorer to copy it somewhere and then read the copy in Notepad. Reading FAHlog-Prev.txt you can do any time with Notepad or any word processor, the client is using FAHlog.txt actively and FAHlog-Prev.txt does not get at all often accessed and the folding client will not care if you make a copy of its current log or another program makes one or if you read its one back (previous) log from last few WUs while client is working away.
HTH.
John.
While client runs, look at client's CURRENT log for enough time that the client wants to write to it. When it cannot and times out after a period of not being able to, it WILL abend suddenly. Linux does not do file lookats this way, and I will explain how because how to do it in Windows will become suddenly quite apparent also (Some of us do fold in Linux, too.).
Linux has this command, called cat and it is short for catalog. ALL this command does is to make a copy of the file it is told to catalog and throw the copy up on the screen but it does so so fast that you cannot read it until the last part is sitting on the screen-- then you just see the end, but I often like to scroll up and down through all of a log for various reasons. Linux has another command, and the cat result can be piped to it. It's called less. Command becomes cat FAHlog.txt | less and les lets you use Page Up and Page Down and Home (top of file, first lines) and Edn and arrow keys to go back and forth as long as you want in a copy of a file sitting in RAM that is made by cat when you do this pipe ( | ) from cat to less.
IMPORTANT POINT which you can make use of in Windows also--cat makes a copy, and you can in Windows also. Then you can read the copy all day, the folding client can write to original, and the folding client will not suddenly choke. So far as I can find out by looking and testing, this behavior is replicable across the Linux and Windows clients through Client Version 5.02. Fixing the client to not choke could be a real PITA of a thing to do. Avoiding this weird issue is not at all bad nor hard to do.
Word and Wordpad can read copies they generate of files that another program (aka application) is using the original one of. So can WordPerfect and Open Office. Notepad normally does not check to see if the file is in use, it just grabs it. Wordpad OFFERS to make a copy if the file appears to be in use, and it can read text files. So, open your current log in one of the programs listed above OTHER tHAN Notepad) and it is likely that if the folding client is on that they will offer to make a copy of the file and let you look at that instead of the original. Let them do this, and the client can write to original while you read a copy made as a snapshot of file at the time you opened your program to read the file. OR, tell Windows Explorer to copy it somewhere and then read the copy in Notepad. Reading FAHlog-Prev.txt you can do any time with Notepad or any word processor, the client is using FAHlog.txt actively and FAHlog-Prev.txt does not get at all often accessed and the folding client will not care if you make a copy of its current log or another program makes one or if you read its one back (previous) log from last few WUs while client is working away.
HTH.
John.
0