Quote from: salsamoves on February 13, 2014, 03:53:26 PM

Quote from: djeZo on February 13, 2014, 03:14:02 PM

Quote from: salsamoves on February 12, 2014, 11:51:48 PM

How do I setup for vert and jane n factor?

Use different (forked) cgminer - usually you can get it in a thread where new coin is advertised.

aha, I thought so, just want sure. and is it correct that we can only advertise it one scrypt/nfacter ect at a time?

I suppose it means a whole lot more programming for you to have more than one as they will all be priced differently! Although on the other side, you are particularly good at programming!

You can only advertise for one algorithm, never for more. Reasons are simple; my service can't swap your cgminers (there is no such API in cgminer) and you may have different pricing plans for different algorithms.

But I gave all providers ability to swap between algos quickly. Just look what market needs and put on what is needed to max your profit. That is all.

Quote from: Squirreljester on February 13, 2014, 07:14:15 PM

OK, I have a dedicated rig that's Linux, and I'm using CGRemote to monitor it. I had this all set up and working fine, before I got CGRemote. Now I can't figure out how to set them both up to work together. Here's my old line:

./cgminer --api-groups P:switchpool:addpool:removepool:restart:* --api-listen --api-allow P:89.212.242.33 --api-port 7777 --scrypt blah blah card config blah

So, P is the leaserig group, and I've gathered that I need to make another group for CGRemote, we'll use W. So, I've got (LOCALIP in place of my local IP address, I don't want to post that):

./cgminer --api-groups P:switchpool:addpool:removepool:restart:* --api-listen --api-allow P:89.212.242.33,W:LOCALIP --api-port 7777 --scrypt blah blah card config blah

The only thing I'm confused about is the port part. Page 2 of this thread is where I got this config from, except for how to enter the port. Do I have to specify that group W uses port 4028 or no because it's a default port? How do I tell --api-port that group P uses 7777 and group W uses 4028? Or is the entry "W:LOCALIP" enough for it to accept access from that IP using the default 4028 port? Don't you have to at least define that W group in the --api-groups string?

Port can be one only. All remote connections will use that port, no matter from which IP.