1
Keyhotee / Re: Keyhotee Status Update
« on: January 15, 2014, 02:58:24 am »
Is it possible to release a statically linked linux client, or should I drudge through the dependency hell until I get it compiled?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Nothing but rejects so far, I'll mine til I wake back up and see if/what anything changes.
Nicely done with the MPOS pool.
Hey guys I was wondering if anyone could help me out.
I'm mining on amazon servers using Ubuntu as the OS. I created an image that has everything set for mining all I need to do is launch an instance (server), SSH into that server and type in:
./memoryminer -poolip=mmc.xpool.xram.co -poolport=1339 -pooluser=.......................etc
Is there anyway to make the miner start automatically without having to SSH into each server?
I was thinking of adding that command in the "Advanced details" at the bottom of the page where you set your max spot price and other options.
Would that work?
Thanks.
sudo crontab -e
@reboot /path/to/memoryminer -poolip=mmc.xpool.xram.co -poolport=1339 -pooluser=<your MMC wallet address> -genproclimit=<number of cpus>
If anyone can get ByteMaster's Coyote Miner to compile, I can help with porting it to MemoryCoin -
https://github.com/InvictusInnovations/coyote_miner
Candidates for a memorycoin pool server
Good candatites for pool servers are the simplier ones like, pushpool https://github.com/jgarzik/pushpool adding the method that memorycoin uses could be possible. Also p2pool https://github.com/forrestv/p2pool which is python based, should be easier to work with, since it's you know python. I've been digging around but haven't come up with much yet.
I've start to look for a pool software too. But pushpool not simple for me, I've start test with eloipool.
Memorycoin work with both getwork and getblocktemplate protocols.
Not simple but not impossible :-)
FaSan
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1
-listen Accept connections from outside (default: 1 if no -proxy or -connect)