Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.



LOL! Just as I read this one of my x64 CentOS VM's started uploading a 50MB monster. Need a fatter pipe.












I just discovered something about the hanging problem. I always thought the problem was that the client wasn't shutting down one of the A2 core processes. I was mistaken about that. As I was watching the process list on a client which was just finishing up I saw that all the A2 core processes were stopped and no longer present in the process list.
I figured that the client was going to grab a new work unit and start running again. It seems I was mistaken. It did not download a new work unit and was stuck like usual. Looking at the process list there was a rogue A2 core process sitting there. As usual, after killing the core process it downloaded a new work unit and started up again.
Just thought I would pass that tidbit of information along.
![]()



Installed 2 vmware notfred clients yesterday and i got 2 a2core projects, 2668 and 2669. For some reason fahmon went bat shit crazy and said one of the was 127xxx% complete and after a while just said both clients were hung. Fah spy worked for a while then one client said it was giving 6xxx ppd by itself. If faspy was correct i was getting around 2000-2100 ppd per client on my stock Q6600.

Installed 2 vmware notfred clients yesterday and i got 2 a2core projects, 2668 and 2669. For some reason fahmon went bat shit crazy and said one of the was 127xxx% complete and after a while just said both clients were hung. Fah spy worked for a while then one client said it was giving 6xxx ppd by itself. If faspy was correct i was getting around 2000-2100 ppd per client on my stock Q6600.
![]()

I've seen some weird happenings with regards to monitoring A2 core work units. I think I've seen something like the 127% deal before but it eventually recovered. Also, there have been some clients which were showing in Fahmon only about half the PPD the clients were actually running. One of my clients used to do this all the time. It would show the client only producing around 1400PPD when in reality it was producing 2800PPD. I checked the frame times and they matched up with the frame times of similar work units. I know it had nothing to do with the clocks in the VMs, although that is a known "problem". It also hasn't happened in about a week or so. I don't know what, if anything, was fixed; but it's not happening currently.
![]()
