Folding Forum

uncle_fungus wrote:FahMon 2.3.2beta2 is up: http://fahmon.net/news/archives/2008/01 ... _29_56.txt

ICE_9 wrote:Sometimes. I will have to test it again to see if it's working correctly. BTW, is their a way to fix FAHmon from closing when I switch users then switch back, or when I remote in from remote desktop?

toTOW wrote:This beta solved the issues with WebApp fields

bollix47 wrote:Compiled new beta on Ubuntu 7.10 and all went well. Noticed that on the display the second computer (Atlantis) is showing some of the times from the first computer. Also, the effective time on Challenger1 looks wrong to me but I'm no expert in these things.
The 7mn+ per frame would be nice on Atlantis(E6600) but it's not likely to happen any time soon.

EDIT: I checked the Eff times using the last version of FAHMON and both are much higher on the beta.

Ooh, that looks like some impressive incompetence on my part, sorry about that.

The effective times may be affected by a timezone offset bug that I'm looking into at the moment, see here: http://trac.fahmon.net/ticket/87

ICE_9 wrote:My html output seems wierd.

http://home.orbitelcom.com/cweldridge/stats.html

Mainly because it says 1760 points points.

Do I need to report that as a bug, and how do I do that?

Hyperlife wrote:Did 2.3.2b change the method for determining a WU's exact download time? There now seems to be a discrepancy in the reported download time when compared to unitinfo.txt on some WUs, but not all of them.

It's not off by much, but I thought I should bring it up. Let me know if you want a bug report filed for this.

This is a separate issue from the time zone offset problem, of course.

[uncle_fungus@Iguana CPU1]$ ./qd | grep issue
  issue: Fri Nov  2 11:30:05 2007; begin: Fri Nov  2 11:30:10 2007
  issue: Sun Nov  4 04:00:57 2007; begin: Sun Nov  4 04:00:58 2007
  issue: Tue Nov  6 18:10:37 2007; begin: Tue Nov  6 18:10:45 2007
  issue: Thu Nov 15 08:19:31 2007; begin: Thu Nov 15 08:19:56 2007
  issue: Tue Nov 20 13:39:36 2007; begin: Tue Nov 20 13:40:23 2007
  issue: Wed Nov 28 16:57:57 2007; begin: Wed Nov 28 16:57:58 2007
  issue: Tue Dec  4 16:29:47 2007; begin: Tue Dec  4 16:29:27 2007
  issue: Sun Dec 23 08:13:02 2007; begin: Sun Dec 23 08:06:39 2007
  issue: Sat Dec 29 05:35:50 2007; begin: Sat Dec 29 05:35:51 2007
  issue: Tue Jan  8 20:26:02 2008; begin: Tue Jan  8 20:28:57 2008

uncle_fungus wrote:Yes, version 2.3.2 uses the queue file to retrieve that information now. Unitinfo.txt is only used as a fallback for working out the % complete if it's impossible to get that from the logfile.

toTOW wrote:FAHmon beta2 crashed when I finished a p2619 (A2 core) ... (it was a gen 3 WU ... completition was at 400%)

I was unable to restart FAHmon unless it gets a new WU (it got a 2653).

uncle_fungus wrote:Can I assume from the lack of comments that the high CPU usage bug(s) and the location corruption bugs are no longer present in the betas?

If so, I've got one more beta to release (which if you're clever you can already download) then it can go public...once I've finished improving the documentation that is

dicecca112{LR} wrote:

uncle_fungus wrote:Can I assume from the lack of comments that the high CPU usage bug(s) and the location corruption bugs are no longer present in the betas?

If so, I've got one more beta to release (which if you're clever you can already download) then it can go public...once I've finished improving the documentation that is

I think I have b1 (it might be 2 though), and its working great. I can test b3 or whatever you haven't released to the public if you PM me how.