• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Diskless Folders - Client Hang Update Information

Status
Not open for further replies.

EvilAlchemist

2[H]4U
Joined
Jan 11, 2008
Messages
2,732
Update ***** New Version is now available!!!!! *****

http://reilly.homeip.net/folding/


Quote from Notfred on hang check issue:
OK, I just found (and fixed) the bug in the hang check.

It's actually nothing to do with the newer version of the client or the logfile, and the bug is actually present in the 11th January version as well, it would not have been present in the 28th November version. It was when I fixed "1853661 - Hang check kills all on > 4 processors", changed from just doing a killall on the cores to walking the /proc tree and looking for the right cores and killing them individually. Buggy code is:

Code: Select all
for procdir in `find /proc -name '[1-9]*' | awk '/\/proc\/[1-9]*$/ {print $0}'`

The problem is that it is only going to work for processes with 1-9 in them. I was just debugging and my 4 cores were 677-680, it only found the first three of them because 680 has a 0 in it. Fix is to change it to:

Code: Select all
for procdir in `find /proc -name '[0-9]*' | awk '/\/proc\/[0-9]*$/ {print $0}'`

This is why it will have worked for some time and then failed to do the hang check because it will depend on what the process id is. I suspect that the last version just happened to end up with process ids containing 0 more often and so that's why the hang check was failing.

I want to address "1903637 - Add kill link to homepage" and "1870815 - Allow SMP per 2 CPUs" before I release a new version, but those should be relatively simple. Depending on how busy I am over the next few days, I should get something out relatively soon.

It is great he has figured out why the hang check would not kick in.
He hopes in a few days to have the updated CD available.

He has already uploaded the new source code to his tracking site so the wait is almost over
 
Now if there was a way to fix the hang issue in Windoze automatically. Lost 7 hours of folding on one of my boxen because it hung. :mad:
 
Now if there was a way to fix the hang issue in Windoze automatically. Lost 7 hours of folding on one of my boxen because it hung. :mad:

Crazy Larry, if your box often hang under windows, it's easy to make 2 new scheduled tasks running each 6 hours. The first task is to kill all the processes with the command "taskkill /F /T /IM mpiexec.exe" (/F = forced, /T = children processes, which is all the FahCore processes and /IM = process name). The second task is to restart the client.

This is what I did with the laptops at work because coworkers often mess with the wireless router or connections drop out of the blue someetime. With these 2 tasks, they can fold no matter what, even if I'm not there to watch.

 
Status
Not open for further replies.
Back
Top