the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2.   Anyone else getting the same?

Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.

yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.

With 0.8.2 the API server is not always started as set by the command line.

Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks

+1 on API fix, good miner but unusable by most of us in actual state!

It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly