So I have now tried the standard MPH_EQUIHASH switcher, MPH_ETHASH switcher and the SALFTER_MPH_PROFIT switchers from nvOC.
I have not yet tried the WTM switcher. That's next. 
I auto_exchange to ZEC on the MPH pool and that also works very well.
I have noticed from my test runs that I gain very little additional ZEC, if any additional, using these switchers than just pointing all my GPUs directly at ZEC.

It seems that the switching occurs often and is based on something like instantaneous profit margin on an exchange.
If that is what is happening, there is very little chance to:
have the miners switch
get the coin mined
into the wallet
confirmed
onto the exchange
and the exchange made before the switching equation is no longer valid
 
And frequently the switch formula will select a coin that only has the highest margin for a very short time, so if you make the time between profit checks too long your wasting time mining a suddenly low-profit coin.
It would seem that auto switching would be more advantageous if one had many rigs that could start the profit checking timeout in a staggered manner.
That way it is more likely that only one rig would be stuck mining a short-time-most-profitable coin.

Can someone help me with what I am missing in my thinking?
My farm is not that large so the benefits may be so small that I can't measure them.
The work done on the switchers is fantastic but I don't yet see the benefit.
Thanks.

Be carefull in Mining VIVO coin, i mine it but it seems that his blockchain is pericliting or desynchronize on severals pools.

If you are minning VIVO, Please let US a Message to tell everyone where is the good blockchain.

Because of this désynchonized VIVO blockchain, i prbably loose 0.5 Vivo ...even if bulwarkpool.com confims all blocks it mine on the wrong blockchain. But i think it's not a good solution to resolve.

I just saw thant hashraffinery seems to have the same problem but i'm not sure because they don't precise tha coins they are desynchronized

Please tell everyone what pool your are using.

nvOC v0019-2.0 Community Release - Miner Update Script

@papampi: can this work also with latest rxOC?

I dont have any amd rigs and dont use rxOC
But I think the set of compile miners has same path as rxOC, but others like ethminer, dstm, bminer, ... may have different path in rxOC that should be changed in 3main/1bash or move them to the appropriate location.

Thanks mate
I know how it works, and I can load watchdog manually but couldn't get it to auto start on system boot.
Also no idea which modules to remove from blacklist .

watchdog install fails becauseetc/init.d/gpu by th00bear does not complain to lsb requirements. You need to add the following to the header (from line 3 onwards):

Also there's an unbalanced quote inlib/systemd/system/watchdog.service. The execstartpre line should have a single quote at the end ('):
after that apt-get install watchdog (or apt-get -f install to fix it).

then

#systemctl start watchdog

then check that it's running with

#systemctl status watchdog

and finally enable at boot with

#systemctl enable watchdog

and don't forget to fine-tune withetc/watchdog.conf
also a hardware driver needs to be specified inetc/default/watchdog.
The drivers are inlib/modules/$(uname -r)/kernel/drivers/watchdog
Usually (proper) mainboard manuals have the type of watchdog installed. On intel hardware, usually iTCO_wdt works.
You can use the softdog.ko module, but it's not as effective

After all this, I tried rebooting my nvoc rig and watchdog start is stuck in starting state. If I stop and start it by hand on the console, it will start but it won't start by itself. Perhaps there's an issue related to nvoc or not (my other ubuntu boxes start normally).

I tried looking for a fix for about an hour now, and still nogo. :/

EDIT: RE: Blacklisted modules:
There's no need to remove blacklisted modules.etc/default/watchdog contains the module name to load and watchdog start will load it regardless of blacklist. This is something that cannot be automated because there's not reliable way to know if a hardware watchdog module is present. Some modules load and assume they work, creating thedev/watchdog* devices. Other will check and fail. It's a mess in general.

@papampi:

thedev/watchdog* device is created by the module (one device per loaded module is created).etc/default/watchdog is where you specify the watchdog module to load at watchdog start.

bothetc/init.d/watchdog and the systemctl service look there and load it.

What happens at boot when you use rc.local is that the "start" command gets stuck and never returns. After some time you can do stop and start again and it works then, but not immediately after boot, which is "puzzling" me.

I tried to add a delay (120sec) in rc.local and it won't start watchdog regardless. So I'm trying variations here atm.

Epicly awesome feature, and version 2.0 is so much better, great work!

Do you only mine coins that are on MPH with your personal WTM list?
Or for coins not on MPH do you point to different pools inside nvOC and have them pay out to other places like your own wallet?

Still trying to get some advice on the profit switching question I mentioned a page or so back. 
Thanks!

Having an issue, not sure how to troubleshoot it. I've formatted a new rig with 1.4 and updated it with 2.0, its loaded with EVGA Hybrid SC2 cards and I keep getting this error every few hours


Every time watchdog fails to complete the boot and when I turn the screen on it just shows a thin purple line at the top and a black/blank screen