[ mining os ] nvoc - page 58. | Bitcointalksearch.org

hashmasta83

newbie

Activity: 28

Merit: 1

Quote from: damNmad on February 02, 2018, 07:02:15 PM

Quote from: hashmasta83 on February 02, 2018, 03:46:16 PM

Probably a terrible question but is there a user guide for nvOC? I searched the forum and any files in the OS and couldn't find anything. Trying to find information on setting up SALFTER MPH SWITCHING. Thanks in advance if I should kill myself........

Hey bruv, I'm here to save you from dying.

You just need to select coin name like this :

Quote

COIN="SALFTER_MPH_PROFIT_SWITCHER

You can see that in the coin list at the end.

I agree there should be guides about this, being a community built we need more contributions, hope more people chip in.

So is this meant to be a multi-algo switching rather than coin switching (same algo)? Is it a better switching at estimating most profitable coins? Just trying to get a better sense of the difference between MPH_EQUIHASH and SALFTER. Also got it working today

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: dmz241 on February 02, 2018, 09:43:12 PM

Anychance of adding timetravel algo?

Give us leads and make sure that the mining software installed on nvOC is not enough. It seems to me that one of the software allows to hash this algo. But I'm not sure.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: papampi on February 03, 2018, 12:22:15 PM

Quote from: CryptAtomeTrader44 on February 03, 2018, 12:04:27 PM

Quote from: papampi on February 03, 2018, 10:50:23 AM

First of all I should thank you for your nice tone... and sorry for nicehash bugs in 1bash, as I said its a pre-release, and usually they have bugs.
I had no intentions of adding Nicehash to my wtm switch as I dont use nicehash but after many users asked for it I followed @CryptAtomeTrader44 instructions on it, and he said that "NICE_" should be changed to "NICE-" in coin name for it to work.

So if you have a fix for it please let us know.

Thanks.
Pap.

Yes, I wrote that there are some post of that.
hurvajs77 had to read it in two or three of my posts a few weeks ago when nicehash returned online after their December BTC hack.

I also had problems with the implementation of these crypto currencies nicehash algo displayed in the list of WTM ...
In fact, I had to review all the 0miner script to check the conditional loops "If" and "fi" I did not notice where I found that it was missing, but what is certain c After doing this, I did not have any more problems with nicehash-algo.
Without this operation, I was entitled to an empty line in the terminal window. He detected that it was nicehash thanks to the python scripts, but did not launch the mining command. As if he did not find it ...

Finally, I asked to replace the underscore in the forked script python papampi because the site WTM uses a dash and not an underscore, which implies that if I want to see the nicehash-algo years the list WTM that recovers that script, I have to put dashes.

Another change request that I made is to change the BTC address used for Nicehash commands to undermine their multi-algo cooperative.
Indeed, nicehash generates its own BTC addresses associated with our accounts nicehash online and therefore you can not directly mine to any BTC address of another site (exchange) or wallet
So I myself replaced this variable in the commands to mine nicehash-algo in NICEHASH_BTC_ADDRESS which is a BTC address for the internal auto exchange on their site, but which can not be a BTC address external to their site and has our personal account.

If this is not clear, do not hesitate to explain what is problematic.

I already made the change as your request and added it in 1bash 19-2.1 pre release :

Code:

NICE_ADDRESS="$NICEHASH_BTC_ADDRESS"

Yes, so it's not a problem, but NICEHASH_BTC_ADDRESS must be in 1bash file of course.

I have not made this update to version 19-2.1 yet

Another thing: I wanted to know what happened to this story of a guy who had posted and which he proposed to share the source of his code with us although he develloped for him initially.

Leenoox had asked him to share his code with graphics and statistics but I do not know if he did something ...

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: hurvajs77 on February 03, 2018, 07:26:22 AM

I've some useful tools for switching, monitoring etc and now doesn't works now.

Can you share these useful tools with us ?

You can not complain that your tools developed for you and by you are no longer operational if you have not shared them and that papampi offers code constantly updated. If it does not have the code, it can not accommodate your changes.

And what are your tools so useful for?

Please explain and share your tools and knowleges with the community please.

joshuajones02

full member

Activity: 210

Merit: 100

Papampi, can you help me out. I'm not sure where to start really but one of my rigs keeps getting a GPU Utilization is too low: restarting 3main error ever so often and it constantly says "connection closed by server r:0". I've tried different pools and different coins but seem to have the same issue. I've also reformatted with a fresh copy of nvOC 19-2.0 but still have issues. Thanks man!

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: CryptAtomeTrader44 on February 03, 2018, 12:04:27 PM

Quote from: papampi on February 03, 2018, 10:50:23 AM

First of all I should thank you for your nice tone... and sorry for nicehash bugs in 1bash, as I said its a pre-release, and usually they have bugs.
I had no intentions of adding Nicehash to my wtm switch as I dont use nicehash but after many users asked for it I followed @CryptAtomeTrader44 instructions on it, and he said that "NICE_" should be changed to "NICE-" in coin name for it to work.

So if you have a fix for it please let us know.

Thanks.
Pap.

Yes, I wrote that there are some post of that.
hurvajs77 had to read it in two or three of my posts a few weeks ago when nicehash returned online after their December BTC hack.

I also had problems with the implementation of these crypto currencies nicehash algo displayed in the list of WTM ...
In fact, I had to review all the 0miner script to check the conditional loops "If" and "fi" I did not notice where I found that it was missing, but what is certain c After doing this, I did not have any more problems with nicehash-algo.
Without this operation, I was entitled to an empty line in the terminal window. He detected that it was nicehash thanks to the python scripts, but did not launch the mining command. As if he did not find it ...

Finally, I asked to replace the underscore in the forked script python papampi because the site WTM uses a dash and not an underscore, which implies that if I want to see the nicehash-algo years the list WTM that recovers that script, I have to put dashes.

Another change request that I made is to change the BTC address used for Nicehash commands to undermine their multi-algo cooperative.
Indeed, nicehash generates its own BTC addresses associated with our accounts nicehash online and therefore you can not directly mine to any BTC address of another site (exchange) or wallet
So I myself replaced this variable in the commands to mine nicehash-algo in NICEHASH_BTC_ADDRESS which is a BTC address for the internal auto exchange on their site, but which can not be a BTC address external to their site and has our personal account.

If this is not clear, do not hesitate to explain what is problematic.

I already made the change as your request and added it in 1bash 19-2.1 pre release :

Code:

NICE_ADDRESS="$NICEHASH_BTC_ADDRESS"

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: papampi on February 03, 2018, 10:50:23 AM

First of all I should thank you for your nice tone... and sorry for nicehash bugs in 1bash, as I said its a pre-release, and usually they have bugs.
I had no intentions of adding Nicehash to my wtm switch as I dont use nicehash but after many users asked for it I followed @CryptAtomeTrader44 instructions on it, and he said that "NICE_" should be changed to "NICE-" in coin name for it to work.

So if you have a fix for it please let us know.

Thanks.
Pap.

Yes, I wrote that there are some post of that.
hurvajs77 had to read it in two or three of my posts a few weeks ago when nicehash returned online after their December BTC hack.

I also had problems with the implementation of these crypto currencies nicehash algo displayed in the list of WTM ...
In fact, I had to review all the 0miner script to check the conditional loops "If" and "fi" I did not notice where I found that it was missing, but what is certain c After doing this, I did not have any more problems with nicehash-algo.
Without this operation, I was entitled to an empty line in the terminal window. He detected that it was nicehash thanks to the python scripts, but did not launch the mining command. As if he did not find it ...

Finally, I asked to replace the underscore in the forked script python papampi because the site WTM uses a dash and not an underscore, which implies that if I want to see the nicehash-algo years the list WTM that recovers that script, I have to put dashes.

Another change request that I made is to change the BTC address used for Nicehash commands to undermine their multi-algo cooperative.
Indeed, nicehash generates its own BTC addresses associated with our accounts nicehash online and therefore you can not directly mine to any BTC address of another site (exchange) or wallet
So I myself replaced this variable in the commands to mine nicehash-algo in NICEHASH_BTC_ADDRESS which is a BTC address for the internal auto exchange on their site, but which can not be a BTC address external to their site and has our personal account.

If this is not clear, do not hesitate to explain what is problematic.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: hurvajs77 on February 03, 2018, 07:26:22 AM

Quote from: papampi on January 28, 2018, 08:54:37 AM

1bash and 0miner v0019-2.1 pre-release changes for Bminer and new coins

Some Changes

Code:

New Coins: LUX, SUMO, DSR, ELLA, XVG, GBX, CRC
Renamed ZM_OR_EWBF to EQUIHASH_MINER
Renamed ETHMINER_or_GENOIL_or_CLAYMORE to ETHASH_MINER
Added BMINER and BMINER_SSL and ANXccminer

Its Better to download and update your 1bash with new 1bash

Or add new coins and Bminer :

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/1bash_19-2.1_pre_release.sh
bash /home/m1/Downloads/1bash_19-2.1_pre_release.sh

Get pre-release 0miner

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/0miner
cp /home/m1/Downloads/0miner /home/m1/0miner

Backup your 1bash and 0miner before update to 19-2.1 pre-release!!!!

I'm very disappointed from this update...

Setting for Nicehash is now very very stupid... :-( Using now 'NICE-' not 'NICE_' as have all coins? 0miner has some mistakes for NH... Didn't work :-( Please, be carefull if change logic of mining coins (I thing there aren't any good reasons for changing coin names). I've some useful tools for switching, monitoring etc and now doesn't works now. I think add new coin and follow actual structure of definition coins and extend other scripts, if it's needed

First of all I should thank you for your nice tone... and sorry for nicehash bugs in 1bash, as I said its a pre-release, and usually they have bugs.
I had no intentions of adding Nicehash to my wtm switch as I dont use nicehash but after many users asked for it I followed @CryptAtomeTrader44 instructions on it, and he said that "NICE_" should be changed to "NICE-" in coin name for it to work.

So if you have a fix for it please let us know.

Thanks.
Pap.

LuKePicci

jr. member

Activity: 128

Merit: 1

I've spent some time in the last few days experimenting with different ethash miners, I found that the easiest way to switch is to make a link named "latest" and point it to the selected miner version. I also had to move the content of the existing "latest" directory in a properly named dir, I don't understand why it hasn't been done this way already. I think the best would be that update script will install new miners in a dedicated directory and update the "latest" link to point the new miner version. Than like it's for claymore in 1bash one should be able to select either "latest" or the exact version. It sounds reasonable or I'm missing something obvious?

hurvajs77

newbie

Activity: 46

Merit: 0

Quote from: papampi on January 28, 2018, 08:54:37 AM

1bash and 0miner v0019-2.1 pre-release changes for Bminer and new coins

Some Changes

Code:

New Coins: LUX, SUMO, DSR, ELLA, XVG, GBX, CRC
Renamed ZM_OR_EWBF to EQUIHASH_MINER
Renamed ETHMINER_or_GENOIL_or_CLAYMORE to ETHASH_MINER
Added BMINER and BMINER_SSL and ANXccminer

Its Better to download and update your 1bash with new 1bash

Or add new coins and Bminer :

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/1bash_19-2.1_pre_release.sh
bash /home/m1/Downloads/1bash_19-2.1_pre_release.sh

Get pre-release 0miner

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/0miner
cp /home/m1/Downloads/0miner /home/m1/0miner

Backup your 1bash and 0miner before update to 19-2.1 pre-release!!!!

I'm very disappointed from this update...

Setting for Nicehash is now very very stupid... :-( Using now 'NICE-' not 'NICE_' as have all coins? 0miner has some mistakes for NH... Didn't work :-( Please, be carefull if change logic of mining coins (I thing there aren't any good reasons for changing coin names). I've some useful tools for switching, monitoring etc and now doesn't works now. I think add new coin and follow actual structure of definition coins and extend other scripts, if it's needed

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

@CryptAtomeTrader44
Thanks for the Merit point Wink

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: joshuajones02 on February 02, 2018, 07:48:58 PM

papampi, does the nvOC 19-2.0 full image have the nvOC 19-1.4 version of linux or is it the newer version that has connectivity issues for some people? Thanks!

It has no problem on my rigs
Test it on a USB stick and see if it has problem or not Wink

dmz241

hero member

Activity: 519

Merit: 502

Anychance of adding timetravel algo?

joshuajones02

full member

Activity: 210

Merit: 100

papampi, does the nvOC 19-2.0 full image have the nvOC 19-1.4 version of linux or is it the newer version that has connectivity issues for some people? Thanks!

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: hashmasta83 on February 02, 2018, 03:46:16 PM

Probably a terrible question but is there a user guide for nvOC? I searched the forum and any files in the OS and couldn't find anything. Trying to find information on setting up SALFTER MPH SWITCHING. Thanks in advance if I should kill myself........

Hey bruv, I'm here to save you from dying.

You just need to select coin name like this :

Quote

COIN="SALFTER_MPH_PROFIT_SWITCHER

You can see that in the coin list at the end.

I agree there should be guides about this, being a community built we need more contributions, hope more people chip in.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: bumbu100 on February 02, 2018, 06:03:25 AM

VeriumMiner Linux Binaries: https://github.com/fireworm71/veriumMiner/releases/download/v1.4/cpuminer_1.4_linux_x64_O2_GCC7.zip
Sources: https://github.com/fireworm71/veriumMiner
syntax: ./cpuminer -o stratum+tcp://eu.vrm.mining-pool.ovh:3032 -u Weblogin.WorkerName -p WorkerPassword

Well that's enough to easily add the minor and modify the mining of Monero with this minor.

Just a question about your Monero miner: You say you are using a virtualization server equipped with 2 Xeon 8 Hearts. But it is known that servers of this type also have large amounts of memories. So your mining software may be better at using RAM.
Cryptonight is also known to be a heavy consumer algorithm of RAM.
How many RAM have your machine ?

[/quote]

Verium is CPU only. I have 16GB RAM available.
Thank you so much.
[/quote]

I think you have to modufy this part of 3main script file code :

Code:

if [ $plusCPU == "YES" ] && [ $AUTO_START_MINER == "YES" ]
then
  HCD='/home/m1/cpuOPT/cpuminer'
  XMRADDR="$XMR_ADDRESS.$XMR_WORKER"
  echo ""
  echo ""
  echo "LAUNCHING:  plusCPU"
  if [[ `ps -ef |grep cpuminer |grep -v grep |wc -l` -eq 0 ]]
  then
    if [ $LOCALorREMOTE == "LOCAL" ]
    then
      guake -n $HCD -r plusCPU -e "$HCD -a cryptonight -o stratum+tcp://$XMR_POOL:$XMR_PORT -u $XMRADDR -p x -t $threadCOUNT"
    else
      screen -dmS plusCPU $HCD -a cryptonight -o stratum+tcp://$XMR_POOL:$XMR_PORT -u $XMRADDR -p x -t $threadCOUNT
    fi
    echo ""
    echo "plusCPU process in guake terminal Tab (f12)"
    echo ""
    running=""
  fi

Code:

  HCD='/home/m1/cpuOPT/cpuminer'

needs to be modified if you replace cpuOPT by verminer.
I will test your miner.

You must add the pools and port parameters too in 1bash.

EDIT, arf, I did not understand that you wanted to mine verium (VRM) with algo Scrypt! I thought you wanted to mine monero (XMR) because you wanted to replace the minor CPU OPT that undermines cryptonight as it is configured in nvOC scripts ... I only realized that when I wanted to register me on one of the pool proposed on the page of your pool which 'no longer accepts registrations.

And suddenly, everything becomes simpler. Just add a section with the mining controls.

On the other hand, there is something else that escapes me: why do you want to undermine scrypt with CPUs, even servers packed with ram in front of ASICs?
This crypto is ASIC compatible and in my opinion it would be much more profitable to mine with Bitmain's machines ... like the L3+ if I remember correctly.
But maybe this crypto currency has implemented ASIC blocking of which I am not aware?

I think these questions deserve answers to be sure you have understood that nvOC is much less powerful for GPU minning than a single ASIC on algo scrypt.

Sorry for giving you false hope ;-)

hashmasta83

newbie

Activity: 28

Merit: 1

Probably a terrible question but is there a user guide for nvOC? I searched the forum and any files in the OS and couldn't find anything. Trying to find information on setting up SALFTER MPH SWITCHING. Thanks in advance if I should kill myself........

Rig4p

newbie

Activity: 59

Merit: 0

Quote from: papampi on February 02, 2018, 01:15:53 PM

Quote from: Rig4p on February 02, 2018, 01:11:45 PM

Quote from: papampi on February 01, 2018, 02:43:57 AM

Quote from: Rig4p on January 31, 2018, 08:28:03 PM

I have been using the nvOC MPH_EQUIHASH coin setup successfully now for several days.
It's a pretty easy setup and switches seamlessly on MPH between Equihash coins on there.

Now I would like to try my hand at using the SALFTER_MPH_PROFIT_SWITCHING setup.
I went through the small changes in 1bash which were basically to set "COIN=SALFTER_MPH_PROFIT_SWITCHING, plus this section:

Code:

########################################################
#                                                      #
# SALFTER_NICEHASH_PROFIT_SWITCHING &                  #
# SALFTER_MPH_PROFIT_SWITCHING Settings                #
#                                                      #
########################################################


CURRENCY=USD

POWER_COST=0.12

MINIMUM_PROFIT=0.1

MPH_USERNAME=xxxxxxxx

PAYMENT_ADDRESS="$BTC_ADDRESS"

WORKER_NAME="$WORKERNAME"

PROFIT_CHECK_TIMEOUT=600

I wasn't sure where to exactly put the port for MPH multi-algo mining so I added it to the MPH_EQUIHASH settings instead of the port I was using for just multi-Equihash coin mining.
I have looked and the /home/m1/mph_config.json file has been created and has my "settings" from 1bash in there but the miners lines all look like default values.

When I start up the miner I see the usual GPU set up lines for power, temp and clocks and a miner is starting message.
My CPU mining starts up in the GUAKE terminal and I see a SALFTER...... tab there as well.
I see a large printout of the profit margins for several coins.
Then a error message and the terminal issues all the GPU stuff again and repeats.
Finally the miner SW shuts down but leaves the HW running. I have to physically reset the rig at this point.

I think I am missing something in 1bash that tells the switcher which algos to allow and I have set the worker up to just run Equihash and Ethash for now in MPH until I get this working.

I read back through the entries here and saw a rather old one by Papampi asking about the SALFTER_MPH function but never saw an answer from SALFTER.

Any help or ideas are appreciated.

Salfter mining launch commands are in 3main.
Open 3main check the miners it use for each algo and manually launch them to see which one has problem.

If you are on 19-2.x you can update and re compile your miners using this post
nvOC v0019-2.0 Community Release - Miner Update Script

In 3main I see this section that helps build the miner commands into the /home/m1/mph_config.json file:

Code:

.................
   "Equihash":
    {
      "bin": "/home/m1/zec/v3_4/miner --eexit 3 --fee 0 --pec --server {HOST} --user {NAME}.{MINER} --pass z --port {PORT}",
      "power_limit": $pwr_lim_equihash, "gpu_oc": $gpu_clks_equihash, "mem_oc": $mem_clks_equihash, "fan": 0,
      "speed": 0.000001140, "power": 0.397
    },
    "Ethash":
    {
      "bin": "/home/m1/eth/ethminer_12dev2/ethminer -S {HOST}:{PORT} -O {NAME}.{MINER}:x -U",
      "power_limit": $pwr_lim_daggerhashimoto, "gpu_oc": $gpu_clks_daggerhashimoto, "mem_oc": $mem_clks_daggerhashimoto, "fan": 0,
      "speed": 0.087, "power": 0.397
    },.....................

But I cannot find where the variables like HOST, NAME, PORT and MINER are pulled from.
I'm sure it's just my limited scripting knowledge that's holding me back.

Thanks.

Hostname and port are extracted from mph web api
Miner location is written after "bin"
You can change them to what suits you best.

Then maybe I see my confusion now.
From reading through the nvOC based "mph_switch" Python code file it appears this function does not use the "built-in" auto-switch function of the MPH website.
If that's the case then the only way to limit the algorithms mined by my miners is to delete them from the Python code.
The Python code appears to use direct mining ports/server paths and NOT the auto-switch ports listed on the website, plus it ignores the auto-switch algorithm selections from the website.
I thought the SALFTER switching in some way used the MPH web based auto-switch setup.
Am I seeing things clearer now?
Thanks.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Bminer updated to v5.3.0

Miners Update Script:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/nvOC_miner_update.sh
bash /home/m1/Downloads/nvOC_miner_update.sh

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: Rig4p on February 02, 2018, 01:11:45 PM

Quote from: papampi on February 01, 2018, 02:43:57 AM

Quote from: Rig4p on January 31, 2018, 08:28:03 PM

I have been using the nvOC MPH_EQUIHASH coin setup successfully now for several days.
It's a pretty easy setup and switches seamlessly on MPH between Equihash coins on there.

Now I would like to try my hand at using the SALFTER_MPH_PROFIT_SWITCHING setup.
I went through the small changes in 1bash which were basically to set "COIN=SALFTER_MPH_PROFIT_SWITCHING, plus this section:

Code:

########################################################
#                                                      #
# SALFTER_NICEHASH_PROFIT_SWITCHING &                  #
# SALFTER_MPH_PROFIT_SWITCHING Settings                #
#                                                      #
########################################################


CURRENCY=USD

POWER_COST=0.12

MINIMUM_PROFIT=0.1

MPH_USERNAME=xxxxxxxx

PAYMENT_ADDRESS="$BTC_ADDRESS"

WORKER_NAME="$WORKERNAME"

PROFIT_CHECK_TIMEOUT=600

I wasn't sure where to exactly put the port for MPH multi-algo mining so I added it to the MPH_EQUIHASH settings instead of the port I was using for just multi-Equihash coin mining.
I have looked and the /home/m1/mph_config.json file has been created and has my "settings" from 1bash in there but the miners lines all look like default values.

When I start up the miner I see the usual GPU set up lines for power, temp and clocks and a miner is starting message.
My CPU mining starts up in the GUAKE terminal and I see a SALFTER...... tab there as well.
I see a large printout of the profit margins for several coins.
Then a error message and the terminal issues all the GPU stuff again and repeats.
Finally the miner SW shuts down but leaves the HW running. I have to physically reset the rig at this point.

I think I am missing something in 1bash that tells the switcher which algos to allow and I have set the worker up to just run Equihash and Ethash for now in MPH until I get this working.

I read back through the entries here and saw a rather old one by Papampi asking about the SALFTER_MPH function but never saw an answer from SALFTER.

Any help or ideas are appreciated.

Salfter mining launch commands are in 3main.
Open 3main check the miners it use for each algo and manually launch them to see which one has problem.

If you are on 19-2.x you can update and re compile your miners using this post
nvOC v0019-2.0 Community Release - Miner Update Script

In 3main I see this section that helps build the miner commands into the /home/m1/mph_config.json file:

Code:

.................
   "Equihash":
    {
      "bin": "/home/m1/zec/v3_4/miner --eexit 3 --fee 0 --pec --server {HOST} --user {NAME}.{MINER} --pass z --port {PORT}",
      "power_limit": $pwr_lim_equihash, "gpu_oc": $gpu_clks_equihash, "mem_oc": $mem_clks_equihash, "fan": 0,
      "speed": 0.000001140, "power": 0.397
    },
    "Ethash":
    {
      "bin": "/home/m1/eth/ethminer_12dev2/ethminer -S {HOST}:{PORT} -O {NAME}.{MINER}:x -U",
      "power_limit": $pwr_lim_daggerhashimoto, "gpu_oc": $gpu_clks_daggerhashimoto, "mem_oc": $mem_clks_daggerhashimoto, "fan": 0,
      "speed": 0.087, "power": 0.397
    },.....................

But I cannot find where the variables like HOST, NAME, PORT and MINER are pulled from.
I'm sure it's just my limited scripting knowledge that's holding me back.

Thanks.

Hostname and port are extracted from mph web api
Miner location is written after "bin"
You can change them to what suits you best.

Topic: [ mining os ] nvoc - page 58. (Read 418529 times)