Multiple pools cgminer Linux?

[giantjoezilla]

So I was mining on give-me-ltc pool last night when it was hit with a DDoS.  After that I found a thread on here that explained how to configure cgminer to use multiple pools, except it was for windows, and I'm running xubuntu. I'm sure I could probably figure it out on my own, but I was hoping someone here might be kind enough to tell me, and save me some time, I would really appreciate it. 

Plus I would really appreciate any advice on my current shell shell script.  I just got some riser cables in the mail to day.  Right now one of my cards does not have enough breathing room, and I have to underclock it.   


#!/bin/sh
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
cd /home/joe/cgminer-3.0.0-x86_64-built
./cgminer --scrypt -o stratum+tcp://stratum.us.give-me-ltc.com:3333 -u USER -p PASS --api-listen --api-network --thread-concurrency 8192  --intensity 17,15,17 --worksize 256 --gpu-reorder --auto-fan --gpu-engine 1050,550,1050 --gpu-memclock 1200,600,1200

[philips]

First post in cgminer´s thread or look in cgminer´s README.
How to add backup pools, pool management and so on.

Basically:

Multiple pool, dedicated miner:

cgminer -o http://pool1:port -u pool1username -p pool1password -o http://pool2:port -u pool2usernmae -p pool2password -I 9

[giantjoezilla]

I'll look.  I did read the SCRYPT-README, and the cgminer thread a few times.  I'll look again.  

I can figure this out on my own.  I have figured out everything up tell now on my own.  I read, and search the the forum.  But sometimes I just want to ask for a little help, and advice.  Just point me in the right direction.  Of course I could figure it out on my own by reading the read me and the cgminer thread, but how long is that going to take?  Someone that already knows how to do it could tell me a fraction of the time it takes me to figure it out.  

Now if you'll excuse me.  I need to pin down my Basset hound, and wash out his ears.  Those long ears get infected easy.

http://3.bp.blogspot.com/_FNQgkfCwYxs/S8xlRfsbu_I/AAAAAAAAAVQ/aO9hqEdvXlU/s1600/Basset+Hound+funny+puppies.JPG  

[philips]

Start with the main readme, scrypt readme is well, scrypt specific.

As I quoted earlier: cgminer -o http://pool1:port -u pool1username -p pool1password -o http://pool2:port -u pool2usernmae -p pool2password ...

While cgminer is running press P and choose a pool management strategy.
Or add the one you choose from:

--balance
--load-balance
--round-robin
--rotate

in cgminer's shell script. (default strategy is failover)

Details for every strategy are in the readme or in the thread.

[giantjoezilla]

Start with the main readme, scrypt readme is well, scrypt specific.

As I quoted earlier: cgminer -o http://pool1:port -u pool1username -p pool1password -o http://pool2:port -u pool2usernmae -p pool2password ...

While cgminer is running press P and choose a pool management strategy.
Or add the one you choose from:

--balance
--load-balance
--round-robin
--rotate

in cgminer's shell script. (default strategy is failover)

Details for every strategy are in the readme or in the thread.

Cool, thank you so much.  Thats what I was thinking it was going to be.  I'll play around with it right after I do laundry and eat dinner.  Any advice on my current shell script?

pm me and I'll send you a ltc for the help.

[philips]

Sorry, I don't mine LTC, try:
https://bitcointalk.org/index.php?topic=117221.msg1256502#msg1256502

Nice dog.

[giantjoezilla]

Thats not my dog, but it looks like him kind of.  My dog is a pound puppy, rescue.  Bassets are good dogs.  I was too busy to upload a pic of my dog.  Maybe I will latter.

[ISAWHIM]

Does "load balance" stay logged-in to multiple pools, sending x-processing to the cards, for each pool?

Seems that it is just pool-hopping still, picking "the most efficient".

I want it to stay logged-in to two/three/four pools, run all pools (speed per pool distributed obviously). So that if one goes offline, that leaves the other cards still connected to the other pools, available to be processing for the remaining pools.

(Thus, not pool-hopping, and loosing earned shares. Thus, not hopping into a pool for x-time, only to have processed useless shares that wouldn't give enough credit to justify having mined there at all.)

Hopping only hurts. Even if it is round robin, or fallback. Continuing where you left off, or increasing an existing running share-level does not hurt us, or the pools. (And it increases our steady-luck, having a foot in every door, makes us have a true average. Actual "returns" without "luck". Luck has been mostly neutralized by pools. Why that is actually conceptually still in the program, is just a waste of code/time. The only purpose of luck is to hurt the majority of others, and reward the minority who did little to get it.)

[giantjoezilla]

When I tested load balancing, It did not increase my hashrate at all.  In fact I think it went down a little.  just FYI

From the cgminer readme

MULTIPOOL

FAILOVER STRATEGIES WITH MULTIPOOL:
A number of different strategies for dealing with multipool setups are
available. Each has their advantages and disadvantages so multiple strategies
are available by user choice, as per the following list:

FAILOVER:
The default strategy is failover. This means that if you input a number of
pools, it will try to use them as a priority list, moving away from the 1st
to the 2nd, 2nd to 3rd and so on. If any of the earlier pools recover, it will
move back to the higher priority ones.

ROUND ROBIN:
This strategy only moves from one pool to the next when the current one falls
idle and makes no attempt to move otherwise.

ROTATE:
This strategy moves at user-defined intervals from one active pool to the next,
skipping pools that are idle.

LOAD BALANCE:
This strategy sends work to all the pools to maintain optimum load. The most
efficient pools will tend to get a lot more shares. If any pool falls idle, the
rest will tend to take up the slack keeping the miner busy.

BALANCE:
This strategy monitors the amount of difficulty 1 shares solved for each pool
and uses it to try to end up doing the same amount of work for all pools.