now where cgminer supports scrypt, can BAMT be used to that also then?
i've like to use BAMT on my LTC mining farm
I have a partway complete tutorial on how to mine LTC with BAMT on my forum. It works, it's tested, but I need to tune it a bit. Basically re-compile cgminer & blammo! It works.
would that mine at the same time as gpu's mining btc?
As per the README, a single instance of cgminer can mine only one LP chain
You need to run 2 cgminers to mine two chains at the same time
Meanwhile ... I've seen comments about BAMT and cgminer 2.6.4 - but it also seems that no one with BAMT know how, wants to sort it out
i.e. I have completely NFI what even is wrong
If it is just a BAMT problem, then fine, but if it is a cgminer problem, then someone who uses BAMT and understands it needs to come visit FreeNode IRC #cgminer
My latest 'linux' change to the API means that when you exit cgminer (properly) and start it again immediately, it will open the API port successfully immediately as long as nothing is still holding the old one open
If it's still held open by a connecting app, then it's the same as before.
i.e. before it would take up to 90s to open the API port, but now if the port is only in TIME_WAIT and closed, it doesn't delay the new one opening (SO_REUSEADDR)
Some possible problems, that would stop this new feature being faster than before (and thus only the same as before), would be:
killing cgminer, rather than quitting it via the API, may hold the port until it times out
running a php script that doesn't exit (php often holds the ports until timeout)
any other app that does the same ...
Also note, that there is no way to actually get around the timeout if the port is held, that's just how sockets work (properly) on linux.
(on windows ... wow that's a different issue, any code can go grab another non privileged socket that wasn't opened with SO_EXCLUSIVEADDRUSE and use it as it pleases, and the original app may not know but will get it back when the offending app closes it)