The following accounts were not paid because they were below the minimum threshold or because the wallet is waiting for blocks to mature.

sending 310212318 to PYCbcdeCMJyGynM7zfBMSJv4eUUHHr8EVV
sending 59656215 to PYKeUGZHJvaZXNt4tr9t71pfBCK4dxiRVk
sending 39770810 to PYTKZhevrkVjRDG41R9Uj4VWk9j6JfYFW6

Where we supposed to post if that was us? I'm the last one: PYTKZhevrkVjRDG41R9Uj4VWk9j6JfYFW6

Quote from: testz on November 09, 2013, 06:32:58 am

Quote from: Amazon on November 09, 2013, 06:31:13 am

Quote from: jbfru45 on November 09, 2013, 05:49:43 am

Quote from: Amazon on November 09, 2013, 05:47:50 am

When I have multiple computers using same payout address, the share number does not scale. Or maybe just my feeling....

I'm seeing the same thing.

Please also check this.

Yes, as I see all computers count as one and probably do the same job, waiting for a fix.

Ok, so the display output parameters you see are for your address and not that instance.  If you have two instances that are both using the same key, then they will both report the same totals and NOT the local totals for that client. 

That is the behavior I have now... if you want a client that tracks its own stats you will need to give it a separate public key.   I will look into per-connection stats.

That makes sense. But it might be worth double checking the other aspect of what he was talking about too; For instance, it almost seemed as if 3 instances using 1 address looked like it may have created PTS or shares about as quickly as 1 instance with 1 address. Which is why he thinks it might be doing the same work if it's using the same address. Of course, none of us were looking that closely, so maybe or maybe not.

Something to double check though. I'm really liking what you have here!

I'm trying the linux version on Debian/Ubuntu. When trying to run it, it says:

/lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.14' not found (required by ./alphaminer)

Anyone know what package that is? There are a lot of libc's in aptitude.

I figured it out. Debian, even the newest, only has GLIB 2.13. I googled to try updating it but everything failed. So I destroyed that and spun up Ubuntu. It's working now.

I'm trying the linux version on Debian/Ubuntu. When trying to run it, it says:

/lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.14' not found (required by ./alphaminer)

Anyone know what package that is? There are a lot of libc's in aptitude.

Is the GLIBC_2.14 version hardcoded into alpha miner? Debian's newest stable version available in the repos is only 2.13-38. I think that might be what it is. http://packages.qa.debian.org/e/eglibc.html The apt package is eglibc-source. My system is fully up to date.

Linux please  Debian 7 64bit. Very nice display btw!

The linux version seems to work well, 93%-100% valid. But the hashpermin is low, it started ~8-9hpm, has gone as low as 1.5hpm, and is now hovering consistently around 3.5-3.8 hpm. Linux 64bit, 8CPU, 16GB, 799% CPU, 34% MEM; 8 processes. 

Is that hashpermin about right? I was expecting ~20.

kenpodragon,

Can you explain please, how is the wallet the same for all instances? I figured there would be a new wallet in each data directory. Or is it because you duplicated the initial one, that they are still the same?

Does that mean you can use commands like "./protoshared getbalance" without specifying a datadir and it will show the results for anything mined from all instances?

Getting about 85+% rejected.