I'll look into the --quiet problem and see if I can reproduce it ...
Yes if you enter nothing in "More Options(Default: --quiet)" you end up with --quiet
That's OK though since the S3 doesn't use screen so you aren't watching cgminer ... and it reduces IO a tiny bit also.
If you really want it to not use --quiet you can put some other option(s) there and it will use that rather than the default --quiet
So e.g. you could add --btc-address 1xxxxx (with your BTC address of course, not 1xxxxx)
if you wanted to set a backup pool to solo-mine at home (and it will have no effect if you don't have any pools pointed at a bitcoind)
Yeah, I thought that maybe (probably out of desperation) the --quiet option was preventing the api from broadcasting the hash rate stats to mmonitor/cryptoglance. I'm not too bothered about the queue setting not being displayed tbh, for the reasons you describe, but it would be nice to be able to connect to & monitor the miner remotely with the software I mentioned above. Is that option not available now?
Thanks again kano.
I wrote the cgminer API.
Various parties have broken it - including Bitmain by changing the names and formats of API replies.
Not enhancements, just simply changing things and breaking compatibility.
Get whoever wrote your monitor tools to properly support the standard cgminer API
If they want to also support the broken API from Bitmain that's up to them.
But the problem is probably both Bitmain and whoever wrote your monitor.
A simple example of the above is that while cgminer has always replied with a number representing MHs in fields called "MHs..." Bitmain replies don't return MHs they return GHs and they changed the names of the fields
... rather than simply dividing the numbers returned by 1000 in their display code (like I've done in my modified S3 code), they changed the API output ... yeah some people don't know what they are doing and should stay away from touching code.
What Bitmain's change means is that you have to support different format replies from different devices.
Though ... the monitor tools shouldn't have problems with that if they've decided to handle the broken replies also ... unless they wont work with anything but Bitmain devices ...