How can I add -q 2 command line param for when bamt starts up phoenix?
EDIT:Here is a conversation I had with El at btcguild about phoenix...
[16:37] <gigavps> @Eleuthria still getting miner idle warnings, since you suggested it was somehow on my end i reset all network equipment
[16:37] <gigavps> [05/10/2011 20:34:26] Phoenix v1.6.2 starting... [05/10/2011 20:34:26] Setting auto kill signal for 180 seconds. [05/10/2011 20:34:26] Connected to server [05/10/2011 20:34:26] Currently on block: 148211 [05/10/2011 20:34:30] Result: 050dafcb accepted [05/10/2011 20:34:33] Result: c74016fc accepted [05/10/2011 20:34:34] Result: 099d91dd accepted [05/10/2011 20:34:45] Result: 6c6bc416 accepted [05/10/2011 20:34:46] Result: 2e039bbe accepted [05/10/2011 20:34:50] Result: 0a9de4ce accepted [05/10/2011 20:35:08
[16:37] <gigavps> [05/10/2011 20:35:51] Warning: work queue empty, miner is idle
[16:41] <@Eleuthria> I'd suggest a better miner if you're running that fast on a single client
[16:41] <gigavps> all gpus are 310-317 Mh/s
[16:42] <gigavps> i using phoenix on bamt
[16:42] <gigavps> are you suggesting that phoenix is not a good miner?
[16:42] <@Eleuthria> Yes.
[16:42] <@Eleuthria> Phoenix is terrible and inefficient, it tosses out a getwork after finding a single share instead of exhausting the space
[16:44] <@Eleuthria> cgminer is better in every way
[16:44] <gigavps> i am all for learning and improving, but why do i not have these problems on other pools like arsbitcoin.com, yourbtc.net, mainframe.nl?
[16:44] <@Eleuthria> But if you insist on using phoenix, add -q 2 or -q 3
[16:45] <@Eleuthria> Because we put you in the back of the line after just feeding you work.
[16:45] <@Eleuthria> So you acn't just spam us with getwork requests.
[16:45] <@Eleuthria> Which is whats happening in your log
[16:45] <@Eleuthria> You finished 3 shares in under 3 seconds
[16:45] <Dyaheon> you're the guy with the 20GH/s operation?
[16:46] <@Eleuthria> On phoenix, that means you're issuing a new getwork multiple times per second
[16:46] <@Eleuthria> Even though a single getwork can contain multiple shares
[16:46] <@Eleuthria> poclbm fixed that, cgminer never had that problem, and my understanding is diablo never had that issue either.
[16:47] <gigavps> do you mind if I post this conversation on the bamt forum topic?
[16:47] <@Eleuthria> bamt?
[16:48] <gigavps>
https://bitcointalk.org/index.php?topic=28967.0[16:48] <@Eleuthria> euh...one of those
[16:49] <gigavps> not sure what you mean
[16:50] <@Eleuthria> Never been a fan of these linuxcoin distros
[16:50] <gigavps> how do you decide when I go to the back of the queue? by worker? by ip address?
[16:50] <gigavps> i run 5 gpus per worker
[16:50] <@Eleuthria> Are you able to add command-line arguments to phoenix in that thing
[16:51] <@Eleuthria> -q 3 would fix it