Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)

@Claymore

Saw this today in my log file:

08:38:29:239   4304   checked ETH share on CPU, spent 4ms
08:38:48:975   43b8   checked ETH share on CPU, spent 3ms
08:39:09:055   43c0   checked ETH share on CPU, spent 3ms

Don`t think that is normal.

Nothing to worry about, this is totally normal.
Look back through your old logs, (use grep for example), and you'll see it's a regular event in the log.
Mr Claymore would be the only person who can explain why he's programmed this, but no doubt there is a logical reason.

Side note: Generally, (assuming the programmer is not a total moron), log entries will have some prefix, or suffix, "warning", "error", "OK", "good" etc etc, which makes life easier when searching logs for problem events, or notable events you might like to check on.

Conversely, if you don't see such annotations, and the log entry is not self explanatory, you can generally ignore such entries. (as in they are not things you need to worry about).

And No, it's not a virus either.

Thanks for your reply iSuX. I was just wondering why is there CPU share

No worries.
I wondered the very same thing when I first saw those entries, but I don't think that means there was a CPU share as such. The CPU is not doing any mining computations in this Claymore, (note the subject header, "GPU miner". My guess was, Claymore has the CPU check the share was delivered, or check summed or against the pool.
Purely a guess though, as I said, Mr Claymore would be the only person who can explain what his intentions are with this, so I could be totally wrong with that guess.

What I can say, is those have been in logs since at least V11.2, although there is no mention of them in the readme or history.

On the subject of Virus, sigh, if you take 2 milliseconds to think about that, and you can probably assume a virus is unlikely to have your best intentions to heart, ergo, it's going to do something you'd rather not have happen, well, it's hardly likely to have the moronic goal of hacking the claymore binary to make it mine with the CPU or advertise itself, by writing it's own log entries.
Hahahaha.